Replies: 163 comments 601 replies
-
|
I'd like to remove the |
Beta Was this translation helpful? Give feedback.
-
|
@D3SL We understand you are frustrated, but replying to every other comment in this thread with the same boilerplate text does not help anyone in the slightest. Please re-enable the legacy action sensors by adding |
Beta Was this translation helpful? Give feedback.
-
I've only replied once in this thread. There are also multiple other threads in parallel to this one where people are separately discussing the same issue, a testament to how severe and widespread of an issue this is. Keep in mind those of us who are already posting here are not only the early updaters but the most technical ones as well, and we're finding ourselves blindsided and crippled by this. A large plurality if not outright majority of Z2M users likely come from the home assistant addon and are not developers with github accounts like those of us posting here are. How do you think this is going for them? As I've said in separate threads: What concerns me more than the way this was handled is the way the fallout is being handled. The outright denigration and scorn being heaped on people who were already technical enough to find their way here for help and answers is deeply concerning, and very reminiscent of the abuse that drove the History Explorer Card developer out of the HA community entirely. It's a very disturbing trend in the overall HA ecosystem. |
Beta Was this translation helpful? Give feedback.
-
|
I meant the whole discussion topic. Replying with the some text does not help. This is an open-source project and most of the workload falls onto the shoulders of a single person, who still has a day job. Literally filling his inbox with walls of angry text does not help at all in this situation. |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to chime in at my own peril. First: Thanks for all your hard work and dedication. I can only imagine the countless iterations on the backend, the long hours, the unthanked "overtime". Thank you for being willing to do all that, and please know there a huge number of people who will never sign up for github just to say thanks, but would likely mean it quite sincerely if they had a path to show their appreciation Second: I do recognize my feelings in @D3SL's comments overall, feels like maybe we got a beta through no malicious intent (you're in good company, HACS and Nabu each had a very rough start to the year, all will continue to bigger and better). That said, I was able to rebuild to a good save point, everything for me clearly broken on version 2+, but what I've not see stated clearly: what even are features and benefits? Of late, new release notes seem to simply reference the new version number (eg notes for 2.x, congratulations, no upgrades to 2x}. As one of the ignorant horde, I've been updating because newer = better. I'm not jumping ship here by any stretch, but it was eye opening enough to not blindly update anymore, this was definitely not a fun weekend for many. Rough, but not insurmountable. Took me years to justify smart home functions to family, not giving up now :) Third: I recognize just how hard it can be to look back to when you were mastering any subject, and I do 100% believe you all have expert level skills and focus, but maybe no longer a filter of what's a deepcut vs truly obvious (eg some recent support says to simply update "configuration.yaml" without clarifying which one, guess where I and many others went first... now assume you're wrong, now assume researching more only to find people still fighting abouts tabs vs spaces, or camelCase or whatever) This third line is not a criticism, simply an observation because I feel I see a thread of people's feelings getting hurt "I didn't mean anything by commenting 'simply," without defining simple to whom. Everything is simple with explicit instructions and a matching skillset, miss either of those requirements and the sky is the limit for frustration I do presume a lot here, but I have always pictured this project being open and welcoming to users of all skill levels. That said, I am at a point I'd love to offer what limited help I can, whether that's near release beta testing (I can at least let you know if I broke my own system with lack of knowledge while at the same time protecting myself with a backup [as a human I sometimes don't wait the 4 minutes to make a backup, especially if I really trust the source, I know, stupid but human])) or somehow helping with communications Fourth: If you're newer to HA/Z2M/any of it and reading this: things breaking is normal, you'll find that they almost always get fixed, and in the meantime backups are key, I personally think still worth moving forward with whatever brought you here, there's a lot to gain, but sadly no one can ever promise no bad days, no matter how skilled Fifth: If in doubt, please re-read First thought Update: Thanks @mundschenk-at for quick response and tips. Just like with firmware, maybe I don't update if not broken and no other compelling reason |
Beta Was this translation helpful? Give feedback.
-
|
@j-and-am There is no distinct beta version per se, but @Koenkk does monthly releases, so normally the changes are not as big as with 2.0.0. If you are using the HA add-on, you can switch to the Personally, I am on a version of the |
Beta Was this translation helpful? Give feedback.
-
|
My suggestion is to remove |
Beta Was this translation helpful? Give feedback.
-
|
added! |
Beta Was this translation helpful? Give feedback.
-
|
I'd also like to remove the duplicate 
|
Beta Was this translation helpful? Give feedback.
-
|
Also added! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
So what's the timeframe for 2.0.0 approximately? (I am asking if I should do a larger clean-up PR for Home Assistant discovery instead of adding Also, wouldn't it be easier if there was a |
Beta Was this translation helpful? Give feedback.
-
|
Lets aim before EOY |
Beta Was this translation helpful? Give feedback.
-
|
It would be great to add to dev console in UI writing and reading numeric (non-standard) cluster attributes. 
Maybe it's not for z2m but for the frontend repo. |
Beta Was this translation helpful? Give feedback.
-
|
How about implementing a tool to translate a valid 1.xx configuration to a valid 2.0 configuration? Possibly with some instructions for porting actually incompatible features, but only when present. The thing I liked about this project was its stability (only since the last 10 or so 1.xy releases). Why would you ruin your (until this decision) great reputation? Software can always be made to be backwards compatible and it's not like that's hard to accomplish (every design patterns book even explains how to do that). It's just not a "cool" thing. Software has utility when it does work and you don't need to track its development. Every second people need to care about you making things "better", is lost productivity. Why are you breaking APIs and existing configurations again (that would want to upgrade to version 2)? |
Beta Was this translation helpful? Give feedback.
-
|
It's literally not a constructive comment. You are just saying something is a fact, without proof. The only valid reason to some extent is that "You don't want to", since I have no rights. (Pretending to act as if you answered the question is just annoying. ) There's nothing to discuss anymore, though. If you had wanted to answer the question, you would have done so the first time. Thanks for the time of stability for as long as it lasted. |
Beta Was this translation helpful? Give feedback.
-
|
@hacscred What kind of hysterics? All breaking changes will be described in the migration guide, legacy parameters can be removed automatically without user intervention. Some small things will have to be fixed manually, but this is the first time in several years for this project. Breaking changes always happen during development to improve the code base and further improve the product itself. Even Home Assistant breaks something in every release (look at any release notes at the end). In the end, no one is stopping you from staying on 1.x.x and migate to a new version whenever it’s convenient for you. |
Beta Was this translation helpful? Give feedback.
-
|
@hacscred From GitHub history, I assume your are not a software developer yourself. That's alright, your concerns are valid nonetheless, and backwards compatibility is something most developers strife for, because it makes life easier for everyone, up to a point. But no, keeping backwards compatibility is not always "not like that's hard to accomplish", and it does come with a maintenance cost. As @Koenkk wrote, sometimes decisions prove to be unwise in retrospect, sometimes the environment (e.g. Home Assistant) has evolved since the original implementation and things have to change. In a lot of these cases, the original functionality has been deprecated for a long time, which means that there is an alternative, preferred way to do things and that notice has been given that the original functionality will be removed at some point in the future. So it's not like this completely out of the blue. As @Drafteed noted, you don't have to change immediately to the new version. Also the necessary changes to your configuration will likely not be as big as it might seem from the technical roadmap if you mainly use Z2M with Home Assistant and directly by MQTT. One point I'd like to add, regarding "I have no rights": You are not a customer. You don't pay developers (@Koenkk and other contributors) to cater to your specific requirements. So yes, you don't have the right to demand a certain outcome. |
Beta Was this translation helpful? Give feedback.
-
|
@mundschenk-at Everything you said is wrong and misguided. Please apologize. @Drafteed Do you ever say something that's not redundant? |
Beta Was this translation helpful? Give feedback.
-
I am a developer and a data analyst. I was completely blindsided by this. Nothing in the changelogs of the home assistant add-on adequately made it clear that literally every single automation I have with zigbee buttons and switches was going to get bricked. If I were to implement a change like this in an R package the standard would be to actively and even intrusively warn the user every time they used something planned for deprecation.
Home Assistant has indeed evolved greatly. It's now more user friendly than ever and is increasingly not a niche tool solely for highly technical hobbyists.
I had many automations tied to zigbee buttons that were trivial to set up with And even that took me a while to figure out because all the mentions of "mqtt" had me going to the "device" entry for these buttons in the MQTT integration... where there's nothing for the action. At all. I program data pipelines in python all day for a living and I spent an hour confused and am now balking at the expected fix. I'm willing to bet a large plurality if not outright majority of users are not nearly as technical as we are and came through the home assistant add-on. All they know is that every button they have is now a paperweight and there's no comprehensive way to fix it.
Nobody is demanding anything. They're simply saying that bricking people's entire houses without remotely adequate warning and no option to replace a trivial call to And as a developer whose published packages people depend on at my day job I agree. I'm rolling back to <2.0 until I can find a replacement. |
Beta Was this translation helpful? Give feedback.
-
|
I am in favor of breaking change for 2.0 and major updates. It is not always possible or desirable to keep old stuff. I have a question about the 1.x z2m.
Is there a policy for z2m ? |
Beta Was this translation helpful? Give feedback.
-
|
My idea is: frozen and not touched anymore (because of time reasons) |
Beta Was this translation helpful? Give feedback.
-
What are those supposed to be replaced by ? I read here that actions are replaced by event, but how would it work with devices like old Ikea remotes, as i don't see events implemented yet ? |
Beta Was this translation helpful? Give feedback.
-
|
The wiki states that the Home Assistant event entity will be the standard and recommended way with 2.0.0 Is this correct? |
Beta Was this translation helpful? Give feedback.
-
|
Hello
I think device_id is less convincing/readable than entity_id. Isn't there such a use case? Regards |
Beta Was this translation helpful? Give feedback.
-
Using device IDs carries some distinct disadvantages when creating a network of automations, as every change of hardware now has to be followed up by a change to a potentially large number of automations. In my setup, I have been using semantic entity names like ‘.[]’ e.g. ‘fan.lounge_ceiling’ or ‘light.kitchen_counter’. These are often addressed from several automations and scripts. Using device IDs breaks this. (And i have strong feelings about that.) @devs, this project has been and is outstanding. And this change - while technologically warranted, I’m sure - needs some work. Home acceptance factors around a great part of the user base have dropped. And who is this project for, without our families having functioning lights? (Rhetorical question, I know of cool, non-home projects where it’s being used) |
Beta Was this translation helpful? Give feedback.
-
|
I couldn't agree more, |
Beta Was this translation helpful? Give feedback.
-
|
I also agree, using |
Beta Was this translation helpful? Give feedback.
-
|
So with Z2M 2.0 , will it be true that I cannot enable permit join via MQTT, wait up to 5 mins for a device to join, interview and configure then disable permit join via MQTT ? |
Beta Was this translation helpful? Give feedback.
-
|
One more question on detail, will 'permit join timeout' kill an existing interview/configure if in progress ? |
Beta Was this translation helpful? Give feedback.
-
|
Interview and configure are extra steps specific to Z2M that are not part of the ZigBee join, hence not affected by the permit join status. |
Beta Was this translation helpful? Give feedback.
-
Carry your phone with you as you travel around the building. Trigger the permit join and check the result from the z2m Frontend on the phone when you standing next to the sensor. |
Beta Was this translation helpful? Give feedback.
-
Great idea - for this you only need to allow phones (which belong into an unprivileged network) to access the otherwise tightly fenced automation vlan. why not just put all crap into a flat network while you're at it... Making those 254seconds the default would have been fine and a sensible decision - flat out preventing any other timeout and breaking permit_join for many people that have an infrastructure that spans over larger areas (and hence multiple z2m instances and zigbee clusters) is just ignorant. We run zigbee networks for various automation tasks in 4 buildings on 3 different sites. In the main site alone it can easily take me 10 minutes to get from my desk to some places in the other building to then install and start pairing a device. The other sites are several kms away and I can't always rely on reaching someone there just in time, so usually I send new devices there with instructions where & how to place/install and how to start pairing; having permit_join active until someone there finds the time to perform the task and the devices show up via mqtt. For now I reverted all related commits that broke permit_join in a forked repository, but I really hope (expect) this will be reverted upstram or at least refined so one can set (much higher) timeouts... |
Beta Was this translation helpful? Give feedback.
-
|
Sounds like you should be running some commercial software. |
Beta Was this translation helpful? Give feedback.
-
|
I've been enjoying Zigbee2MQTT for years now. Many thanks for maintaining such a great product so diligently. Hats off from me. |
Beta Was this translation helpful? Give feedback.
-
|
I look at the proposed changelist and everything is really promising @Koenkk, but one thing i want to put up for discussion, and that is the removal of I myself, and assume a lot of people use other automation platform, for example Node-RED. The HA-NR integration is greate, device triggers also added so basically this change should not be a prolem, right? Sadly, it is, generally as device triggers work, you cannot target multiple device with one selector, in the past I wrote a lot of common subflow/function that use the generic state triggers and filters entities by regex, because I use consistent naming for my entities, not really need to deploy 100s of device triggers just use, for example this regex: Can we at least shift the deprecation of this action/click entities because i assume that i not the only one that has such a use-case. |
Beta Was this translation helpful? Give feedback.
-
|
@mundschenk-at let's try to do at least 1.X release with the event support before releasing 2.X |
Beta Was this translation helpful? Give feedback.
-
|
It would be really nice, thank you. 🤲 |
Beta Was this translation helpful? Give feedback.
-
Yes, this would be a great idea. This would allow time to the community to see if there is any problem and anticipate the change👍 For sure, I would love to able to test already as some of my HA blueprints are a nightmare to change with a MQTT trigger without errors...🥴 |
Beta Was this translation helpful? Give feedback.
-
|
@chris-1243 We are still hashing out some details, but I've opened a documentation PR where you can see how it will work. |
Beta Was this translation helpful? Give feedback.
-
|
I had a look. Thanks for your effort. I hope you may provide a I will need to crash some automations to understand more precisely (some blueprint I made...🤫) |
Beta Was this translation helpful? Give feedback.
-
|
I may have missed this elsewhere, but I think it's worth coming up with a plan for the What if:
|
Beta Was this translation helpful? Give feedback.
-
|
This will also be a bad experience. First you will need to switch to Probably the best solution would be to display warnings (in logs, in release notes, etc.) about upcoming breaking changes when using legacy functionality, such as legacy sensors. Like in Home Assistant, which displays deprecated messages in logs for several months and generates a system issue. |
Beta Was this translation helpful? Give feedback.
-
|
I have been using Zigbee2mqtt for years. Many thanks and my respect for your great work. |
Beta Was this translation helpful? Give feedback.
-
|
You can already do that, just set a different |
Beta Was this translation helpful? Give feedback.
-
|
It would be good if some of the changes can be brought forward into v1 to enable people to migrate their configs off legacy sooner - e.g. introduce the change to update sensors alongside the current setup. |
Beta Was this translation helpful? Give feedback.
-
|
Have a look to this thread. It is expected👍 |
Beta Was this translation helpful? Give feedback.
-
|
This is probably the bottom of your list of priorities, but can we see some UI/UX improvements? thanks |
Beta Was this translation helpful? Give feedback.
-
|
Not for 2.0, the frontend is maintained in a separate project (not by me) |
Beta Was this translation helpful? Give feedback.
-
|
Breaking compatibility with ezsp devices without an upgrade path for hacked Silvercrest/Lidl devices with Silicon Labs chips in them, is just contributing to a huge pile of electronic waste without any justification. If you actually knew what you were doing, you wouldn't remove support for devices that work perfectly (uptime/availability measured in years). One major point of trust in a software project, is that once support for a device exists and there are users that want to use such a device, you make it compatible for whatever features were available previously. If someone credible were to fork zigbee2mqtt or make an independent different implementation (also independent of HA), then I would have no reason not to switch, since you already have broken that basic trust. Probably I will just buy a couple of replacement devices, but I would never have bought that e-waste if zigbee2mqtt hadn't supported it earlier. Why should I buy anything you recommend now? There's such a thing as credibility and you already lost it. |
Beta Was this translation helpful? Give feedback.
-
|
@ReneTode Oh you're wasting your time reasoning with him. His girlfriend took the kids and fled to her mother's a few days ago and he hasn't got anyone to beat the crap out of so he's been hanging around here venting his spleen sprouting utter tosh and being abusive to anyone who doesn't align with his truculent babbling. I hope he doesn't own any small animals! |
Beta Was this translation helpful? Give feedback.
-
I don't think he has kids, if he does I'm worried. I think it's because his mother has given him house arrest 🫢 |
Beta Was this translation helpful? Give feedback.
-
|
@MSL-DA I feel sorry for the mother then! I'd be ashamed if I pushed that out and keep it under house arrest also! |
Beta Was this translation helpful? Give feedback.
-
|
Please explain the existence of #22520 then. |
Beta Was this translation helpful? Give feedback.
-
|
very simple. someone did use it and had a problem just like you. if you use a hack, then dont complain that others dont support it. make sure it works again, or find the person that hacked it in the first place and complain there. EVERY device in the SUPPORTED adapter list is still supported. (even though there are some you better not use) |
Beta Was this translation helpful? Give feedback.
-
|
Why does there seem to be no explanation around why changing to device triggers via mqtt is now preferred? Surely there has to be a reason |
Beta Was this translation helpful? Give feedback.
-
|
@bobmarley2021 See a psychiatrist, since you need one. |
Beta Was this translation helpful? Give feedback.
-
|
@hacscred Thanks for your concern 👍 Same to you, you have some serious alignment issues with life and how to talk to others. |
Beta Was this translation helpful? Give feedback.
-
|
@bobmarley2021 Because I don't align to you? That seems like a feature, not an issue. I have superior verbal abilities. I know perfectly well how to talk to others in about five languages. It seems you see problems when there aren't any. You, on the other hand, seems to think that there are never consequences to your actions. Sooner or later you will find out when you meet the wrong person and what makes you so sure that I am not that wrong person? I think you are the one with an issue. |
Beta Was this translation helpful? Give feedback.
-
|
@hacscred you might be able to talk in 5 languages, but talking is different then communicating. i only did see from you in here, but all i see is attacking, attacking attacking and complaining about things you did cause yourself. and you might not like it but not everything can be solved after you made bad choices in the past. |
Beta Was this translation helpful? Give feedback.
-
For real? I know people who speak 12+ languages fluently and don't think they are a superior being. Get down off your high horse 🤣
Oh I do see problems yes, but they definitely are there. It's your crappy attitude and how to talk to others. Your arrogance, your superiority complex, your disrespect for others here including our host, Koen.
What? Where on earth did you get that from? I take full ownership of my actions and stand by each word I've said. Luckily I try not to hang around with thugs and thankfully only come across them on the internet. Never before on github like this I must admit but there's a first time for everything.
You do, do you? :) Well good for you. Do you know, I think this is the most benign thing you've said yet. I mean you're clearly still deluded, but at least you're toning down the attacking somewhat and starting to communicate more like the rest of the class. I mean, you haven't told anyone they shouldn't have been born or that they're incompetent, redundant or should get a divorce for at least a few hours. Well done you :) ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
What was the reason to drop the mqtt config API for |
Beta Was this translation helpful? Give feedback.
-
|
its just moved. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Was wondering as it is listed as removed in the OP. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
i have no idea how to fix my thing i tried both Ember and Zstack and i get errors, i have a sonoff dongle 3.0 Plus this is the error code i get now |
Beta Was this translation helpful? Give feedback.
-
|
That error message is horrendous, but I am sure the development team has some silly excuse for their incompetence like "the software is free, so our users need to suffer". My recommendation is to buy a different adapter and just remove anything made by Sonoff from your house. You may not agree, but I tested three smart plugs and every single one if them was awful compared to the competition. So, why would anything else that is more complex work well then? The proper solution would have been to include in the error message a proof of why one state is not "consistent" and that would only be the beginning. |
Beta Was this translation helpful? Give feedback.
-
|
Hey Wotner82. Maybe the channels are out of sync ? 11 - 25 / |
Beta Was this translation helpful? Give feedback.
-
|
I deleted the these lines: " from the configuration.yaml, then I got errors like yours, so I wrote it again and the errors did not appear. |
Beta Was this translation helpful? Give feedback.
-
|
@mmarts if you get simular errors, then most likely you did something wrong with the change. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for not reading everything here before posting but there is quite a lot going on here.... I have no issues and just want to ask one question. I just upgraded to 2.0.0-2 and made damn sure to follow this guide (no issues at all, network with 70+ devices, all works, great work to everyone involved!) I did however notice one thing, I am 100% sure I had this in my configuration file before upgrade. After upgrade however it's not present any more, I would assume this is expected and it's gone since it's now "default values"? Hopefully someone can confirm my thinking, otherwise I need to add it again and restart Z2M I guess. |
Beta Was this translation helpful? Give feedback.
-
|
Upgraded to version 2 with 62 devices without any issues. Yes these are removed from configuration.yml after upgrade. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Koenkk, thanks for the release! When do you plan to roll out the next z2m patch release? |
Beta Was this translation helpful? Give feedback.
-
|
every first of Month he releases new Versions |
Beta Was this translation helpful? Give feedback.
-
|
@Koenkk thanks for the update, working wonderful so far and I also migrated over to device triggers. I'm really thankful for the work that you do here! However I have one question, I know that you have to press the buttons on remotes (like the IKEA TRADFRI Dimmer) at least once so that Homeassistant picks them up? |
Beta Was this translation helpful? Give feedback.
-
|
@Koenkk and the rest of the team that work on z2m - thank you for everything you do. It's amazing and incredibly generous to the community. My upgrade went perfectly - 70 devices. To those casting shade on the efforts of this project - please uninstall and find another project to haunt. Your negativity is not helpful and not appreciated by anyone. |
Beta Was this translation helpful? Give feedback.
-
|
Hi All, I am trying to understand what I need to do to upgrade. I have read the document and am I right in thinking that all I have to do (as a minimum) is add: to my configuration.yaml, update and reboot? I'm not a super programmer (glorified hobbyist) and it is a little scary reading the document as there is some I don't quite understand 😅. If I have read it right, the biggest change is that some of the attributes have changed names, so my automation's may break until I update them? I am running HA on an X86 with "Home Assistant Operating System". I know I am being dumb but I wanted to check I am taking the right steps before I hit update! |
Beta Was this translation helpful? Give feedback.
-
|
Yes but you also need to add the adapter type. So:
and also:
I don't know how much you like tinkering with new things but something for you to ponder if you're running on X86: You'd love the security and reassurance that Proxmox can provide. Install Proxmox and use Tteck's scripts to install HA OS in a VM (https://community-scripts.github.io/ProxmoxVE/). You can export your HA config beforehand and re-import (install to a different HD if you can). You'll need to pass through your USB adapter and don't forget to change the repos to CE. Before anything like this you can just snapshot it, then if it all goes Pete Tong you click a button and it's back as it was. The Z2M add-on backup should be sufficient for now but Proxmox has saved me when an update causes HA OS not to come ready again. I snap before any HA updates, then only delete them when I am sure everything is ok. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome thank you! I think I will do this when my partner is away for work just in case it all goes pear-shaped and I have to play around with it. I have backups for upgrades going back months lol I only ever delete them when I am sure all is working 😄 Also have full system backups daily and hold them for a few weeks as well. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds like you have good policies in place. So perhaps hold off on v2 for a second if you're concerned until your partner is away like you say, get up to speed with Proxmox, then once you're migrated over (if you feel comfortable with it and you want to do so) you can mess around with v2 as much as you like and if you do accidentally do something wrong with the config, or it doesn't migrate over, you've at least got the snapshots to take it back to exactly where it was. I run Proxmox on 3 machines with several VMs and a load of LXC containers and it's really quite a stress reducer! I regularly make use of snapshots to undo either user error or botched updates of various apps. Once you get up to speed is Proxmox and how it works I'm sure you'll love it. You can even run their backup server if you're totally paranoid. :) |
Beta Was this translation helpful? Give feedback.
-
|
Issue with Zigbee2MQTT 2.0.0 Upgrade and Rollback to Version 1.42** |
Beta Was this translation helpful? Give feedback.
-
|
I'm even more scared to upgrade now! |
Beta Was this translation helpful? Give feedback.
-
|
Don't worry! |
Beta Was this translation helpful? Give feedback.
-
|
@voltkj This is so hyper-specific that it borders on wrong. (Also blocking updates of Z2M in itself does nothing at all regarding "missing entities" in HA.) |
Beta Was this translation helpful? Give feedback.
-
|
You're right! Blocking updates in AdGuard Home won’t directly fix the issue with missing action entities in Home Assistant. However, it prevents automatic updates to potentially unstable versions of Zigbee2MQTT, which could cause device compatibility issues—like the one I encountered with Loginovo ZG-101ZL and Tuya TS0044. The missing action entities are most likely related to changes in device converters or integration between Zigbee2MQTT and Home Assistant. For now, staying on version 1.42 keeps everything stable. Thanks for pointing this out! It’s important to be precise. 😊 |
Beta Was this translation helpful? Give feedback.
-
|
Can you not just turn off auto-updates? It is what I have done while I try to understand the process and my machine is still happily running 1.42 |
Beta Was this translation helpful? Give feedback.
-
|
You're absolutely right! Disabling auto-updates works—but only up to a point. In my case, Home Assistant forced the Zigbee2MQTT update within 24 hours, even though I had auto-updates turned off. That's why I had to block updates through AdGuard Home as an extra layer of protection. |
Beta Was this translation helpful? Give feedback.
-
|
@chipnotic See my above comment about Proxmox. It's a lifesaver. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the suggestion! I've heard a lot of good things about Proxmox, but I haven't fully explored it yet. The idea of using snapshots for quick rollbacks sounds really useful, especially when testing major updates like Zigbee2MQTT v2.0.0. Once I have some more time, I’ll definitely look into setting it up. Having that extra layer of protection would definitely make experimenting with updates less stressful. Thanks for the tip! 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I actually already have Home Assistant and Zigbee2MQTT running on Proxmox. 😊 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the suggestion! I actually already tried adding those configurations (legacy: false, adapter type, and all advanced options). You can see my full troubleshooting process above. Unfortunately, even after applying these settings and restarting Zigbee2MQTT and Home Assistant OS, the action entities were still missing, and devices like Loginovo ZG-101ZL and Tuya TS0044 weren't working correctly. In the end, rolling back to version 1.42 was the only solution that fully restored functionality. But I appreciate the input! 👍 |
Beta Was this translation helpful? Give feedback.
-
|
For the Tuya TS0044, all standard entities like: sensor.0xa4c1389d81bb8db7_linkquality sensor.biurko_toshiba_action If needed, I can share logs or screenshots to show how it behaved across versions. Let me know! 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, I no longer have the logs since I reverted back to Zigbee2MQTT 1.42.0-2 and the system cleanup removed previous logs. However, I can describe the issue clearly: In version 2.0.0-2, all standard entities like: sensor.0xa4c1389d81bb8db7_linkquality sensor.biurko_toshiba_action If the issue happens again, I will make sure to save the logs for further analysis. Thanks for understanding! 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Assuming that |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I did add legacy_action_sensor: true to the homeassistant section in the Zigbee2MQTT configuration and restarted Z2M afterward. Unfortunately, the sensor.biurko_toshiba_action entity still didn’t appear in version 2.0.0. I also checked for the entity under both: sensor.biurko_toshiba_action (friendly name) Since I've already rolled back to version 1.42, I don’t have the debug logs anymore. If I decide to upgrade again, I’ll make sure to capture the logs for further analysis. Thanks for your help! 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Regarding zigbee2mqtt/Wtyczka_zibee_2, there were no issues in the logs. The device correctly published MQTT data, and its state was properly reported: 2025-01-18 10:33:00 z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Wtyczka_zibee_2', payload '{"child_lock":"UNLOCK","current":0,"energy":6.4,"indicator_mode":"on/off","linkquality":88,"power":0,"state":"OFF"}' |
Beta Was this translation helpful? Give feedback.
-
|
It’s quite clear that some people have had issues with the upgrade. I suspect not a lot of people actually read release notes, and something as big as “breaking changes” should stand out. I understand some people may have had some unhappy family members when all they want is for things to “just work”, but reading and understanding more will probably help. There are also plenty of people commenting about how they are experts in coding and logic, but not a single one of them has forked or submitted PRs. I completed the upgrade yesterday, and have not had a single problem as yet. For a moment I thought I lost a device, but turns out it was playing up before the upgrade and just needed a restart, which is a known problem for that device. Good job guys, keep up the good work! |
Beta Was this translation helpful? Give feedback.
-
|
I completely understand your point, and I agree that reading release notes is important. However, not everyone using Home Assistant or Zigbee2MQTT is a programmer or has the technical skills to analyze breaking changes in detail. It’s the responsibility of developers to anticipate potential issues and provide clear, user-friendly guidance—especially when introducing major updates. That's why many projects release alpha, beta, and stable versions to catch bugs and avoid impacting daily users. While advanced users can troubleshoot or contribute code, most people just want their smart home to work reliably. The key is finding a balance between innovation and stability. 😊 |
Beta Was this translation helpful? Give feedback.
and others
-
This discussion contains a list of breaking changes for Zigbee2MQTT 2.0.0.
Tip
Most of the breaking changes are about removing legacy features that have been deprecated for years (replaced & improved since), and as such, automatically disabled for newer networks.
How to get prepared (before updating to 2.0.0)?
In order to get the minimal amount of breaking changes when upgrading from 1.x.x to 2.0.0, make sure you have the following in your Zigbee2MQTT
configuration.yaml:Also it is recommended to explicitly add a
serial.adapterto yourconfiguration.yaml, see #24364 for more info.Important
Check you current
configuration.yaml, it is likely that some of these values are already present, and set tofalse, if your network is recent enough (past few years). The breaking changes marked with: Only breaking when legacy is enabled can be ignored if your configuration already has these values set tofalse.Breaking changes
General
USB adapter discovery error (No valid USB adapter found), see Z2M 2.0.0: `USB adapter discovery error (No valid USB adapter found)` #24364 how to fix this.zstackis no longer the default foradaptersetting. If Zigbee2MQTT fails to start saying the adapter could not be discovered, it means your adapter uses an identification not currently recognized by Zigbee2MQTT, make sure to specify theadaptersetting if that's the case.Bare-metal installations (no Docker/Home Assistant add-on)
configuration.yamlfrom repo, this will result in the following error when updating:git checkout data/configuration.example.yaml mv data/configuration.yaml data/configuration.yaml.bak ./update.sh # (update as you usually do) mv data/configuration.yaml.bak data/configuration.yamlpnpmis now used instead ofnpm, the installation instructions andupdate.shscript has been updated accordingly. For existing installations you need to executenpm install -g pnpmbefore updating../update.shscript, make sure you pull changes from git withgit pull --no-rebase(after stopping Zigbee2MQTT).pnpm run clean, then start Zigbee2MQTT again.Home Assistant
update_stateandupdate_availableentities have been removed (succeeded by theupdateentities).homeassistantproperty, useexposesinstead.sensor/selectforselect/number/buttonentities, the full list of removed entities per model can be found here.hass/statusHome Assistant status topic anymore,homeassistant/statusis used instead (ifhomeassistant.status_topicis not set in your Z2Mconfiguration.yaml). Double check that Home Assistant is using this status topic by going to: HA -> Settings -> Devices & services -> MQTT -> Configure -> Re-configure MQTT -> Next; the Birth message topic should behomeassistant/status.homeassistant.legacy_triggerssetting). This means allsensor.*_clickentities are removed. Use the MQTT device trigger instead.sensor.*_actionentities). It's recommended to use the MQTT device trigger instead. In case you really need the action sensors, add the following to yourconfiguration.yaml.homeassistant.legacy_entity_attributessetting) has been removed. This means that entities discovered by Zigbee2MQTT will no longer have entity attributes (Home Assistant entity attributes are accessed via e.g.states.binary_sensor.my_sensor.attributes).Device specific
child_lockon/off values have been changed fromtrue/falsetoLOCK/UNLOCK.illuminance_luxtoilluminance, this breaks in two ways:illuminance_luxhas been removed and the value ofilluminancechanges. Home Assistant users might have to manually enable this sensor via Home Assistant. This affects the following devices: 83633205, MOSZB-140, MOSZB-153, EFEKTA_iAQ3, EFEKTA_PWS_Max, EFEKTA_PWS_MaxPro, EFEKTA_eON29wz, EFEKTA_eFlower_Pro, EFEKTA_iAQ, E2134, POK004, POK011, ROB_200-070-0, HK-SENSOR-4IN1-A, AU-A1ZBPIRS, RADON TriTech ZB, TS0601_illuminance_temperature_humidity_sensor_1, TS0202_3, S-LUX-ZB, TS0222_light, THE01860A, TS0222, LCZ030, MIR-HE200-TY, XFY-CGQ-ZIGB, TS0601_smart_human_presence_sensor_1, Y1_IN, ZY-M100-S_1, ZY-M100-S_2, WZ-M100, ZG-205ZL, ZG-204ZM, YXZBRB58, ZY-M100-24G, ZY-M100-24GV2, ZY-M100-24GV3, MTG075-ZB-RL, RT_ZCZ03Z, ZY-M100-S_3, ZG-205Z, 8750001213, HSE2927E, ZB003-X, 07502L, JS-MC-SENSOR-ZB, KK-ES-J01W, KMPCIL_RES005, RTCGQ11LM, RTCGQ12LM, b-parasite, 7A-SS-ZABC-H0, 5AA-SS-ZA-H0, RTCGQ14LM, RTCGQ15LM, ZNCLBL01LM, GZCGQ01LM, GZCGQ11LM, 07047L, 9290012607, 9290019758, 9290030675, 9290030674, 545D6306, CCT595011, ZSS-ZK-THL, 4512770, TERNCY-PP01, MBD-S, CTM_MBD_Dim, 3RSNL02043Z, WB-MSW-ZIGBEE v.3, MS100, USM-300ZB, PIR313-E.switchexpose andactionvalues have been changed, see the device docs for the new values.device_options.legacy. These breaking changes below can be ignored if you havedevice_options.legacy: falsein yourconfiguration.yaml:button_*properties.duration,rate,brightnessandtransition.duration.step_size,transition_timeand the following actions:play_pause,skip_forward,skip_backward,rotate_*.rotate_*actions.button_*properties and removedsingleaction.singleaction.left,rightandbothaction (including the*_longand*_doubleactions).to_side,from_side,angle.angle.repeat,useranddata.duration.step_size,transition_timeandskip_*actions.actionvalues have been changed, see the device docs for the new values.keypad_lockoutvalue changedsetpoint_change_source,setpoint_change_source_timestamp,remote_sensingandcontrol_sequence_of_operationvalues are now mapped values (string) instead of a number.operation,setpoint_change_source,setpoint_change_source_timestamp,remote_sensingandcontrol_sequence_of_operationvalues are now mapped values (string) instead of a number.directionandnumberweekly_schedulepayload.action, removeddurationandcounter.click.External converters and extensions
external_converterssetting is no longer used. Instead all external converters insidedata/external_convertersdirectory are now automatically loaded. Make sure to move all your external converters to this directory.data/external_extensionsinstead ofdata/extension. Make sure to rename yourdata/extensiondirectory (if present) todata/external_extensions.MQTT api
update_availableproperty from the device state has been removed (useupdate.stateinstead).updateAvailabletoupdate_availableinzigbee2mqtt/bridge/response/device/ota_update/check.zigbee2mqtt/bridge/request/device/bind,zigbee2mqtt/bridge/request/group/members/add,zigbee2mqtt/bridge/request/group/members/removeandbridge/request/device/configure_reporting, the endpoint has been moved to theendpointproperty and cannot be set via thedevice/fromproperty anymore.zigbee2mqtt/bridge/request/configMQTT API, this includes the following MQTT topics:zigbee2mqtt/bridge/request/config/last_seenzigbee2mqtt/bridge/request/config/elapsedzigbee2mqtt/bridge/request/config/log_levelzigbee2mqtt/bridge/request/config/homeassistantdatapayload in the response is now always empty when there is anerror, this affectszigbee2mqtt/bridge/response/device/configureandzigbee2mqtt/bridge/response/device/ota_update/*.permit_join_timeouthas been removed fromzigbee2mqtt/bridge/info, it has been replaced bypermit_join_endwhich represents the Unix timestamp when permit joining will end.advanced.legacy_apisetting), this includes the following MQTT topics:zigbee2mqtt/bridge/logzigbee2mqtt/bridge/(bind|unbind)zigbee2mqtt/bridge/group/*zigbee2mqtt/bridge/networkmap/*zigbee2mqtt/bridge/ota_updatezigbee2mqtt/bridge/device/DEVICE_FRIENDLY_NAME/get_group_membershipzigbee2mqtt/bridge/config/*zigbee2mqtt/bridge/configureRemoved features and settings
Important
The new configuration update system will automatically (re)move deprecated settings the first time you start Z2M after updating to 2.0.0. Make sure to check the
data/migration-1-to-2.logafter startup. See the docs for more info.advanced.reportsetting).advanced.soft_reset_timeoutsetting).devices.IEEE_ADDR.options.retrieve_statesetting).availability_timeout,availability_blocklist,availability_passlist,availability_blacklist,availability_whitelistandadvanced.legacy_availability_payload(see availability docs for the new settings).advanced.legacy_availability_payload,zigbee2mqtt/bridge/statewill now always be a JSON object ({"state":"online"}or{"state":"offline"}).permit_joinsetting has been removed, use the frontend or MQTT to permit joining.configuration.yaml(groups.devicessetting). This will not impact current group members; however, you will no longer be able to add or remove devices from a group through theconfiguration.yaml.ota.ikea_ota_use_test_urloption has been removed.advanced.homeassistant_discovery_topicis now inhomeassistant.discovery_topicadvanced.homeassistant_status_topicis now inhomeassistant.status_topicadvanced.baudrateis now inserial.baudrateadvanced.rtsctsis now inserial.rtsctsexperimental.transmit_poweris now inadvanced.transmit_powerexperimental.outputis now inadvanced.outputwhitelistis now inpasslistbanis now inblocklistexperimentalsection no longer existsPull requests
retrieve_statezigbee2mqtt.io#3075readAfterWriteTimezigbee-herdsman-converters#8089configuration.yamlzigbee2mqtt.io#3104configuration.yaml#24338illuminance_luxzigbee-herdsman-converters#8304maximum_packet_sizeMQTT setting zigbee2mqtt.io#3228datain response is always empty onerror#24971sensor/selectforselect/number/buttonentities #25026permit_join_timeout#25082homeassistant.status_topictohomeassistant/status#25286Beta Was this translation helpful? Give feedback.
All reactions