-
Notifications
You must be signed in to change notification settings - Fork 663
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Device does not re-appear in Home Assisant after reconnect on reboot of HA+MQTT-server #2190
Comments
Please provide the debug log file. Also Screenshot of the HA MQTT device. Also you should check using another MQTT client if the topics get sent. I usually use http://mqtt-explorer.com/ |
|
Debug log Development-Branch: fix-timezone-config-parser (Commit: d9cb0e1d66af170c1175dd7fdc2531fb2ee71260+):
|
Homeassistant uses the topic Please update to 15.1.0 and check the logs there. Please note that it is not suggested to restart HA and the MQTT broker every night. This means you will lose messages during that time! |
I tried by manual publishing the connected payload to the AHwatermeter/connection topic. But is does not bring it back online. |
v15.1.0 says: (Only send Homeassistant Discovery the first time we connect, ...) |
No, HA only needs to receive the discovery topics once, so it can set the device representation up. |
You can test the HA behaviour by sending "connection lost" resp. "connected" to "AHwatermeter/connection" using another MQTT client. |
But when the HA restarts.. it needs those again.. the AI-on-the-Edge device does not "know" if HA had restarted or just lost the connection... |
Then your HA is setup quite odly! |
It looks like HA keeps the devices but they will not re-appear online after they are offline for some minutes unless you re-send the auto-discovery sequence... |
What do you mean "not re-appear"? After a MQTT timeout (which is set to 2.5 of the Round interval), the MQTT broker will send the Last Will Topic which is "connection lost". HA will then mark all entries of that device as "not available". After the device completes a round, it publish the "connection" topic with "connected" and HA will show the entries as "available" again. Sending the Discovery topics is completely independent of this! And as a side note, there are many users with HA, if there would be such a bug, you for sure would not be the only one complaining! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
The Problem
Since i upgraded to Development-Branch: fix-timezone-config-parser (Commit: d9cb0e1+) my devices do reconnect and report to Home-Assistant but it does not show. After the HA-server and MQTT have restarted (they do it every night in my case). Before i used version v15.0.3 (Commit: f42e9c7+) and with that version it works fine.
It looks like there is a slight difference in the MQTT reconnect procedure...
Version
Development-Branch: fix-timezone-config-parser (Commit: d9cb0e1+)
Logfile
Will be supplied if neccesary
Expected Behavior
No response
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: