-
Notifications
You must be signed in to change notification settings - Fork 663
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
Home Assistant Status Unavailable due to MQTT Topic Connection: Lost #3306
Comments
Are you using TLS for MQTT? There seem to be a communication error with the MQTT broker. I improved the error logging, please give it a try:
|
Maybe related: #3289 |
Yes, #3289 may be related. Regarding 1: no TLS is in use Regarding 2: I will give it a try when I am at home in 1 h. Thanks! BR Frank |
Hello again, MQTT Log is empty. I am using eclipse-mosquitto:latest in docker on SynologyNAS DS1520+ DSM 7.2.1-69057 Update 5: Here is the Log from Build Build and Pack #3116: Commit [4e1df4a]
During the time the same behaviour: Hope it helps. Thanks, Frank |
The problem is that this ID actually sais that there is no error, so I have no clue what it means :( |
I think I found the problem. FYI: I have 3 water meter units. I was able to activate the logging in MQTT and it says that it is closing the connection when another watermeter connects, because it thinks that they are all one client. I have then put in a different client ID for every watermeter and now it is stable. I think I had this configured in the previous stable release, but since OTA-Update of all 3 units to 16.0 RC1 forced me to create a new config file I must have missed that. So I think there is nothing more to do and we can close this issue. Thanks for the support! BR Frank |
yes, the MQTT client IDs must be unique. And there is no way the devices cold check/handle this. |
The Problem
Since 16.0 RC1 the MQTT Topic Connection is "Connection lost" ~1-10 sec after transmitting the values.
Because of that HA says Status is unavailable.
Version
Release: 16.0.0-RC2 (Commit: 3708698+)
Logfile
Expected Behavior
Connection-Topic not being lost
Screenshots
Screenshots are in the Description of the problem, see above.
Additional Context
First occured in 16.0 RC1
The text was updated successfully, but these errors were encountered: