Release 1.35.2 · Koenkk/zigbee2mqtt · GitHub
Release 1.35.2 · Koenkk/zigbee2mqtt · GitHub
Improvements #6930 Support multi endpoint for generate definition (@ffenix113) #6969 Update all Lumi (Aqara and Xiaomi) terminology, device vendor and description (@mrskycriper) #19847 Support mor...
You're viewing a single thread.
Seems like a big update - do most Z2M updates include this many fixes/additions? I’m new to Z2M and am hesitant about updating unless I see a fix that will directly affect me positively.
Can anyone here report if they’re having any issues after updating? Looking at the comments, a number of people are reporting their devices not working shortly after updating, but idk if10 or so people posting is a large or small percentage of the user base.
That seems like a lot of new features for x.x.1 update
Ideally, in SemVer, I believe xx1 updates would just be bug fixes that are unlikely to have any regressive impacts. It should be the absolute safest to update to automatically.
No hate to the developer, but Zigbee2mqtt doesn't really do semver. Features are released in patches and there are no backports of bug fixes to previous versions. I'm running Zigbee2mqtt on NixOS and had to use the unstable nixpkgs branch to make sure I was getting the latest bug fixes.
But yeah no hard feelings, it's still a really amazing project that's done so much for home automation.
Didn’t noticed any problems with version 1.35.2-1. So you are safe to go…. But always make a backup of HA.
From what I've seen from running it the last year or so, yes, most Z2M releases add/change a large number of things. I use the Docker container, and I backup my mapped data directory between releases, but I have had no release related issues. Sometimes new items or features appear in Homeassistant, but it has always worked for me.
Updated and no issues so far.
Thanks for confirming you had no issues (along with everyone else’s responses!). I took the plunge and updated yesterday and so far no issues apart from my inovelli switch triggers still missing. Luckily someone made an automation blueprint that circumvents this issue but it would still be nice to have that back! And to be fair, idk if that’s an MQTT issue or an issue with the 2.15 firmware on the switch.