MQTT `/forecast/` überfüllt UI Log, dadurch keine weiteren Log Einträge vorhanden

[VolkerK62]

Das ist alles was angezeigt wird. (Laptop und Smartphone getestet)
Im level "Trace" gibt es auch entsprechende "httpd" und "mqtt" Einträge. Mehr aber nicht.
sudo journalctl -fau evcc liefert alle Einträge wie gewohnt.

Version v0.314.0-dev+5ab5cfc2e

Zustand war aber auch mit Nightly von vor 2 Tagen so.

[github-actions]

Thanks for the report. I looked into the log-viewer pipeline (server/http_site_handler.go logHandler, util/logstash/log.go) and think I found a very plausible explanation, but would like confirmation before calling it a confirmed bug.

Likely cause: the UI log view only requests the most recent 1000 lines by default (DEFAULT_COUNT in assets/js/views/Log.vue, count param in logHandler). The ring buffer itself holds up to 10000 lines total, shared across all areas.

Both httpd and mqtt log at TRACE level on every single request/message:

• server/http.go:69 — logs every incoming HTTP request (log.TRACE.Printf("%s %s", r.Method, r.URL.Path))
• plugin/mqtt/client.go:245 / :293 — logs every MQTT publish/receive (m.log.TRACE.Printf("send %s: ...") / "recv %s: ...")

publishComplex in server/mqtt.go recursively fans a single site/loadpoint update out into many individual MQTT topic publishes, so a handful of state changes can easily produce hundreds of mqtt trace lines per update cycle. Combined with httpd trace lines for every poll, these two areas alone can push well over 1000 lines through the ring buffer within seconds at Trace level — evicting/out-scrolling entries from all other, much less chatty, areas from both the visible window and eventually the ring buffer itself.

Could you confirm:

1. Do you have MQTT enabled/connected in your config, with the log view still on Trace?
2. Does clicking "Alle Einträge anzeigen" / "Show all" at the top of the log view reveal entries from other areas (further back in the buffer), or is it truly empty for everything except httpd/mqtt even then?
3. Does selecting a lower level (e.g. Debug) bring other areas back?

That would confirm whether this is "other areas simply got crowded out by TRACE-level httpd/mqtt noise" (a UX/verbosity issue) versus an actual bug where entries never make it into the ring buffer at all.

🤖 Generated with Claude Code

[VolkerK62]

MQTT is enabled and with level trace the log is showing entries for mqtt and httpd.
Going back to Debug did not change the areas. Only httpd and mqtt are available.

[VolkerK62]

Problem is, that these 10k lines are filled by mqtt within 2 seconds.
The most entries are filled with forecast/temperature (about 4000 lines) , forecast/planner , forecast/grid and forecast/feedin

[mqtt  ] TRACE 2026/08/10 06:10:36 send evcc/site/forecast/temperature/532: '3'
[mqtt  ] TRACE 2026/08/10 06:10:36 send evcc/site/forecast/temperature/546: '3'
[mqtt  ] TRACE 2026/08/10 06:10:36 send evcc/site/forecast/temperature/532/1: '1786193100'
[mqtt  ] TRACE 2026/08/10 06:10:36 send evcc/site/forecast/temperature/532/2: '1786194000'
[mqtt  ] TRACE 2026/08/10 06:10:36 send evcc/site/forecast/temperature/532/3: '30.7'
[mqtt  ] TRACE 2026/08/10 06:10:36 send evcc/site/forecast/temperature/720/2: '1786363200'
[mqtt  ] TRACE 2026/08/10 06:10:36 send evcc/site/forecast/temperature/720/3: '34.2'
[mqtt  ] TRACE 2026/08/10 06:10:36 send evcc/site/forecast/temperature/721: '3'

[VolkerK62]

Komplettes Trace Log mit 10k Zeilen

evcc-20260810-061038-trace.log

[VolkerK62]

Prima, jetzt hat man sogar ein längeres debug Log zur Verfügung.

Aber so richtig war das noch nicht die Lösung.
Bedingt durch die vielen "forecast" Meldungen per MQTT, fehlt im Trace z.B. die Auswahl für das Auto oder die Wallbox.
Da muss man dann immer wieder aktualisieren und Glück haben, dass der Bereich irgendwann angezeigt wird und auswählbar ist.

[andig]

Das lässt sich nicht sinnvoll ändern- wenn du mqtt willst dann sind das die Logs :/.

[VolkerK62]

ok, wollte nur darauf hinweisen. Ich hab ja zur Not noch journalctl.

[andig]

Argh. Warte mal. Was sind das überhaupt für komische Werte? Die braucht ja kein Mensch und falls doch dann als json! Ich vermute das ist in #32391 kaputt gegangen.