You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally reported by: Scott Wilson (Bitbucket: Scotty86, GitHub: Scotty86)
MQTT messages are being sent on the network with the prefix homeassistant/light/{name}/config and homeassistant/switch/{name}/config even though in the configuration homeassistant is turned off. The messages have no content.
The text was updated successfully, but these errors were encountered:
That's a known "behavior". Since MQTT messages sent by ESPurna have the retain flag set to true by default, those messages stick and Home Assistant receives the old configuration message when it restarts even if you have disabled it on ESPurna. The way to solve this is to overwrite that retained message with a blank one. The broker will then remove the message from it's retained database and Home Assistant won't receive it again.
The only solution I can think off is to have a button on the web UI to manually delete that message (send an empty message).
Another option, send the empty message only one when the user disables that feature. The message gets queued if no MQTT connection available. It will always send a discovery message on boot if enabled. There is one corner case: no MQTT connection, the user disables home assistant and then resets the board. The empty message will not be sent in this situation. The user will have to enable and disable it again. I think this is a minor problem.
Originally reported by: Scott Wilson (Bitbucket: Scotty86, GitHub: Scotty86)
MQTT messages are being sent on the network with the prefix homeassistant/light/{name}/config and homeassistant/switch/{name}/config even though in the configuration homeassistant is turned off. The messages have no content.
The text was updated successfully, but these errors were encountered: