Seems a few people have this problem with every release, but usually only a few.
This has happened to me a few times (major problems when most have no issues). Every time I had something wrong in my configuration that went unnoticed until error checking/etc. improved, and then it breaks.
I can’t really think of a great solution for this, you can’t have logs set to debug level for everything all the time and it’s impossible to test every feature of a complex setup after every upgrade.
Yes you have the problem already, but it only appears if you have many MQTT entities.
Regardless, the bug is still there and you will eventually face it.
Here’s the problem. I likely have a backup sitting somewhere that is prior to the MQTT update. Guess what though? I have no idea which one it is. They’re all full backups and many things have changed which renders the full backups useless. After the MQTT update, everything worked fine so I didn’t think there was a problem. All until the reboot of HA 4-5 months later and now it’s clear this is a critical problem. The fact that you’re a mod here and are very dismissive of any concerns is not a great way to run a community. I think you need to mature a bit before you make your next comment.
How about this, fix the problem at hand. Place an upgrade to MQTT that regresses the core mosquito version back to before this was an issue. OR even better, just make it so we can terminal in and revert the MQTT version ourselves. Backups are great, but they’re not the best way to handle this problem. Many people didn’t even know this was an issue until they rebooted, some of us don’t reboot for 5-6 months at a time. This is not acceptable. Why would HA run an MQTT beta version anyway? This was beta dev, not production.
Thank you. Sure hope the MyQ integration has been updated and fixed with this release.
When you installed the mqtt add-on update it would have made a partial backup. This will be a smaller size than your full backups and will have a description you can read in home assistant or you can look inside the backup with 7zip or similar software to see what it contains.
Even if you can’t find that partial backup you can partially restore a full backup from before the update to only restore the mqtt add-on.
Guys with the mosquito broker issues, why dont you fork the addon repository to your own GitHub, load it as custom, and change the config file to the previous version?? No restore from backup needed?
Or just copy the mosquito folder to your local addon share , and change there the version, so you can install the previous version
I just did a fresh install of home assistant. Thus no backups. I am experiencing very odd behaviour with Zigbee2MQTT. The front end won’t load and says I need to restart Z2M. However, everything is working. If I click on the side bar link, I will 7/10 times get that error. If I click on the “open Web UI” from the add-on page, I will be able to open Z2M about 8/10 times. Restarting does not fix the problem.
I previously used Z2M before with no issues so this behaviour is odd and very inconsistant. It appears to be with the frontend only? This whole back and forth is confusing and I am not sure how to fix the problem. I am running Supervised Debian 12 full supported. Is rolling back the MQTT broker the fix? If so, without backups what is the easiest way to change to an old version.
Who on earth are you replying to?
I think that Nabu Casa / HA devs make it hard for Z2M on purpose just to push their favored ZHA instead. Looks like politics over functionality - which is very bad in my opinion.
Thinking about canceling my paid subscription.
You are very vague. How is it made hard to use?
Just wanted to say: Hi 
Looks like baseless accusations over facts - which is very bad in my opinion.
Kind regards,
…/Frenck
A Zigbee2MQTT user and occassional contributor as well
Very nice update once again. Works perfectly. Thank you to all the HA team and beta testers 
NICE WORK!! 
Blacky 
PS: The voice is realy starting to move. This is insane development and fully local… LOVE IT!! 
we love you
I don’t see that at all. As a long-time ZHA user, I sometimes feel like I’m being left behind. These forums are full of advice to ditch ZHA and set up Z2M. From what I’ve heard, it supports more complex functionality than ZHA does, and gets a lot more developer attention.
For the record, ZHA does everything I need (pretty basic stuff, to be fair.) I don’t want or need to add the complexity (and the associated learning curve and maintenance overhead) of both MQTT and Z2M. But if I found myself needing more functionality, I know there’s a well-supported option there.
as someone who has used deconz, ZHA, and then Z2M I have no idea what you are talking about. Z2M is working great and I’ve never had any issues with it, I don’t know in what way the HA devs would even be capable of “making it hard for Z2M”
Just ignore those kind of people
Also consider that it’s Nabu casa employees workkng on philips hue integration. Which is also zigbee. Assume good intentions…
According to my test.
Turn of bluetooth, Device shows “not home” after 10 mins for both iPhone and Apple Watch.
Bring device left home, it also took 10 mins to be not home.
When back home or turn on bluetooth, Device shows home immediately.
One iPhone 14 Pro Max got strange behavior, when lock screen it will change to not home after 10mins.
When wake screen, it changes to home.
Anyone can help to explain more or tip on how to troubleshoot this?
Thanks
Since the 2023.10.3 update both my rfxcom integration and my Zigbee2Mqtt integration are failing.
Do get quite some errors in the logs (aiohttp cannot write to closing transport, various other odd errors). Will roll back a backup.
Edit: apparently my USB hub decided it was time to die at the exact time at which I installed 2023.10.3. Replacing the USB hub fixed the problem.
mqtt completely dead for me too, do i have to revert ?
