New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FATAL errors during startup are not reported over mqtt #12890
Comments
@thomas-hutterer-tik gibts den nur auf MQTT nicht oder gar nicht (auch nicht /api/state)? Schaust Du unter |
das /api/state liefert in dem Fall 404: pi@raspberrypi:~ $ journalctl -o cat -fu evcc auf mqtt gibt es eine /site/error topic aber kein /site/fatal |
Kann gut sein, dass das Beenden im Fall von |
wäre fein wenn das geändert wird, damit wir das mit bekommen und eine Fehlermeldung anzeigen können |
Naja- nachdem Du den Prozess mit |
ich habe journalctl mit ^C beendet. Der evcc process hat sich zuvor schon selbst beendet. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
HA als OT markiert. Wir halten fest: es gibt keine Indikationen für Crashes. |
Is your feature request related to a problem? Please describe.
when e.g. the IP address of a configured wall box changes, evcc dies in the startup process with a message like
Mar 12 19:43:20 iWattControllerV3 evcc[36822]: [main ] FATAL 2024/03/12 19:43:20 cannot create charger 'OpenWbSeries2-1': cannot create charger type 'template': cannot create charger type 'openwb': error connecting: network Error : dial tcp 192.168.10.31:1883: i/o timeout
Describe the solution you'd like
I would like to see fatal errors reported over the mqtt interface, to my service will be able to react and report this further to the user
Describe alternatives you've considered
I considered parsing the log file of the evcc process, but this seems like a tedious and solution as we do all the other communication via the mqtt interface
Additional context
not using the evcc UI, but our mobile and web app
The text was updated successfully, but these errors were encountered: