-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
MQTT Discovery in HA throws an error after upgrade to 2024.7.3 - MQTT settings lost after reboot #1882
Comments
All of a sudden, EMS-ESP had "forgotten" the MQTT configuration and switched it off as well. Weird. |
Fixed |
this is strange. I'm happy it is fixed but would still like to know what may have caused it.
|
Agree, this is really strange. I updated HA yesterday to 2024.7.3 and did not notice anything unusual. This morning, one value from the ESP was missing, so I rebooted HA, just to make sure it was not HA. After the reboot, all values of EMS went offline, so I checked the EMS website, but all looked good. I then rebooted EMS ESP as well, but nothing changed. After finally rebooting Mosquitto I filed the issue. |
Thanks for explaining. This has happened to me before as well, it's very odd and I really don't know what is causing it. Sometimes the MQTT settings are removed or not being loaded after a re-boot of EMS-ESP. It's mentioned before in the last 1-2 years, like in #1265 (comment). I just don't know what is causing it. This is one to keep track of. Thanks for reporting. |
Just to clarify: I cannot tell for sure, if the MQTT settings had already been deleted BEFORE I rebooted the ESP, as I only checked afterwards. But I would assume they had been gone already beforehand, as there was no other reason on why HA did not receive any data from the ESP. |
PROBLEM DESCRIPTION
MQTT Error is shown in the log. Not sure what it means, but all ESM-ESP Entities are offline in HA
REQUESTED INFORMATION
TO REPRODUCE
Error occurs since update to 2024.07.3
EXPECTED BEHAVIOUR
MQTT should deliver the attributes again
The text was updated successfully, but these errors were encountered: