-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 won't start after HA OS upgrade #3264
Comments
same here, no ones on this issue ? |
After upgrading to OS 11 i have random stops of Zigbee. Sometime al is working fine for a few days en suddenly all Zigbee devices are unavailable. I can restart HA anymore and only remove power. After reboot al is working fine until it is happening again. Before the upgrade Zigbee and HA was rock solid. I use the combination: Log files are not showing anything. |
I could not wait long for a reply. This meant I had to remove and install mosquitto. |
Dear all, I also have the same issue. I've remove at least 3 time mosquitto and re-installed it. That fixes the issue for some time but then it starts again with the same error message:
Something seems wrong. Home assistant OS 11.0 and |
Circling back just to share what i did. What i did is reverted to the backup before the update and went the route of seperating the mqtt from home assistant. |
This is what I'm doing. I move now MQTT to a virtual debian machine with influxdb and Grafana with Promox. |
Your way probably better, im just not a fan of VMs unless you know exactly what youre doing, otherwise lots of simple things can get complicated later when having to deal with those layers. Im old fashioned, my HA is on a NUC, my mqtt on a rpi, they are both battery backed to keep things running at all times |
It might not be the best way but I had a server laying around and found a good use for it. And for the authors of the add-on. I still would like to say thank you. I know open source can be sometimes difficult. Doing stuff in the spear time. So big thank you again. I learnt a lot with it. |
Solution is to uninstall and the re-install mosquitto addon. Configuration |
This wasn't my experience. Uninstalling meant I lost the persistent mosquito database and so all retained messages. I lost a lot of devices since the discovery was deleted. I'm not sure why the devices were deleted since the discovery payloads weren't cleared but that's what happened. |
Did not notice that, as I do not need any persistent currently. |
Is there a quick fix available without reinstalling? |
Same problem here |
If it's any help, I managed to get slightly further with a |
I have the same issue. This didn't work for me. |
I've had a chance to get hold of the persistance db out of the mosquitto addon and have a look using the mosquitto_db_dump tool, and there are some null client IDs in there which kind of makes sense based on the log...
I wonder if there's a mosquitto issue letting null client IDs through but then failing to process them? They were all tasmota related in my db, so that seems worth a look as well. |
I've got into the same issue of error in mosquitto addon: |
Same here.
|
Same issue here. After reinstall it worked again (for now). |
@hackex @CaptainBalou @fsaris do you have any Tasmota devices? That seems to be what caused the problem for me- at least everything has been working since fixing the mosquitto.db and removing the problematic Tasmota device. If not, it would be interesting to see which client has the null id in your case. Unfortunately it's a bit fiddly to find that out, so it might be nice to update the mosquitto addon to (optionally?) log the output of a db_dump at start up? |
Yes, I have tasmota devices. So you expect that one of the devices broke the mosquitto db? |
Same here. I have also Tasmota devices.
|
I can give the feedback I don't have Tasmota devices but I have that issue. I have AI on the Edge. I don't know if that might be a problem aswell. So it might not only be for one device brand only. |
Same problem detected today - even with MQTT 6.4.0. Using Tasmota devices. |
my tasmota devices showing MQTT login errors - nothing changed: did some more investigations: |
The good news is that there's a fix coming soon (hopefully 🤞) from mosquitto which should help... I still think it would be nice if the home assistant addon could include the mosquitto_db_dump tool as well- not really sure where to start but I might attempt to have a look over the Christmas break. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It would be good to use the updated version of mosquitto when it's available, and including the db_dump tool might still be nice to help debug any future problems. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It doesn't look like the mosquitto fix has been released yet. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It looks like there is something wrong with the HA addon that didn't send the client ID to Mosquitto. This leads to broken messages that were persisted by Mosquitto. After a restart, Mosquitto tries to load the persisted messages and fails because of the missing client ID in those messages.
|
For anyone not familiar with terminal commands: This deletes the whole mosquitto DB. The problem messages could be removed from the DB instead of removing everything. |
Thats true, if you know how to open the db file, find the broken message and how to remove this. Removing the full db is simpler. And it is simpler than trying to reistall the complete mosquitto and maybe have to reconfigure that. |
It would be really nice to fix this issue, unfortunately it got closed as stale. There is a fix in mosquitto that will fix the issue with missing client IDs in the persistence file but I don't think it's in a release yet- that's how someone fixed my file rather than deleting it, although deleting it is probably way easier! It would also be good if nothing was sent without a client ID in the first place. |
Describe the issue you are experiencing
After upgrading to HA OS 11.0 MQTT addon won't start
Relates issue
Relates #3253
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Mosquitto broker
What is the version of the add-on?
6.3.1
Steps to reproduce the issue
...
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
No response
Additional information
/mnt/data/supervisor/addons/data/core_mosquitto/options.json
mosquitto/mqtt.conf
The text was updated successfully, but these errors were encountered: