Critical system issues detected

[ridax67]

What happened

The system reported the following issues:

• Battery Monitoring [ERROR]: Critical sensor configuration issue detected
• Energy Monitoring [ERROR]: Critical sensor configuration issue detected

Debug bundle

Please drag-and-drop bess-debug-2026-07-01-053827.md from your Downloads folder into the editor below before submitting.
The file contains your version, settings, recent logs, and the raw HA discovery dump that the maintainers need to reproduce the issue.

[ridax67]

bess-debug-2026-07-01-052523.md

[ridax67]

What are these errors? Which sensor is affected? I don't have influxdb configured in bess. I do have the tou time option list modified, don't know of that could affect something (only starting times 00, 15, 30,45 and ending times 14, 29, 44 and 59).

[bess-agent]

Root-cause diagnosis

Thanks for the debug bundle — it points to two separate bugs on our side, not a sensor misconfiguration on yours.

1. The "Battery Monitoring [ERROR]" / "Energy Monitoring [ERROR]" banner is stale, not live

The dashboard alert banner is driven by a health-check result that's only recomputed when BESS Manager starts up or when you save settings — it's never rechecked automatically afterwards. If your sensors were briefly unavailable (e.g. during a Home Assistant restart) at one of those moments, the ERROR state gets "stuck" showing even after the sensors recover. Your debug bundle confirms this: a fresh health check run at export time shows Overall Status: OK with 0 critical issues, while the banner you saw was reporting the old, unrecovered state. This is a caching bug — the banner needs to self-correct instead of only updating on startup/settings-save.

2. Recurring "Error connecting to InfluxDB" log spam

This is unrelated to the banner, but explains the noise in your logs. BESS Manager ships with a default (placeholder) InfluxDB URL, and one code path that fetches historical data every ~15 minutes doesn't check whether InfluxDB is actually configured with real credentials before trying to connect — unlike the startup path, which does check correctly. The result: it keeps attempting homeassistant.local:8086 every 15 minutes and logging a connection error, even for the many users (including you) who never set up InfluxDB. It's harmless to functionality (schedule/optimization keeps running, it just skips historical "actuals" reconciliation), but it's constant, confusing noise. Your custom TOU time list is not related to either issue.

No action needed on your end — both are bugs in BESS Manager itself. Tagging this bug for a fix; you don't need to provide anything further.

---

Posted by the bess-analyst automated diagnosis agent.