Replies: 152 comments 575 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.
-
|
Ok then i'm already ok, thanks. Since i doubted about that, i may not be the only one to do so, it would be good idea to mention the device trigger doc while talking about this "deprecation". |
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.
-
|
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.
-
|
I urge everyone involved to refrain from any inappropriate accusations, insults, or personal attacks with immediate effect. Even if you may not have the last word on this. Let’s maintain a constructive and respectful tone, even when there are differing opinions. First and foremost, I want to express my deepest appreciation for the incredible work done by the initiators, developers and contributors of Zigbee2MQTT. Their dedication, expertise, and countless hours of effort have made this project an invaluable tool for the community and me personally. The unstoppable progress of Zigbee continues, and combining Zigbee2MQTT with Home Assistant holds enormous promise -perhaps one day even at the enterprise level -for the entire smart home ecosystem. Even if we appear anonymous online, we’re still neighbors who bring diverse backgrounds, skill sets, experiences, and needs to the table. In this spirit, I encourage everyone to reflect on our shared experiences - both positive and challenging - and channel them into ongoing development. Every single one of us can contribute, whether by sharing user stories, testing new features, providing constructive feedback, or writing code. By focusing on solutions and collaborating across our varied perspectives, we can propel this project forward and honor the immense work that has already been invested in Zigbee2MQTT. Thank you all for your commitment and for fostering a positive, respectful, and forward-thinking discussion culture! |
Beta Was this translation helpful? Give feedback.
-
|
What about, appdaemon? how i can subscribe for, for example, scene switch click? |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps my question is unclear.
where "Entities_SceneSwitch" contains something like "sensor.round_button_action"
|
Beta Was this translation helpful? Give feedback.
-
|
You would probably find more expertise on AppDaemon in a dedicated forum. |
Beta Was this translation helpful? Give feedback.
-
|
Middleware like AppDaemon typically lags the software it is in the middle of and in this particular case the addon is independent of even the AppDaemon two man development team. |
Beta Was this translation helpful? Give feedback.
-
|
for appdaemon nothing changes AFAIK, unless you base your automations on HA entities and not on mqtt. @hacscred appdaemon is middleware? do you even know what appdaemon is? |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the great effort!!! I like zigbee2mqtt a lot.. I have the following in my current version 1.42. When I update to 2.0.0 my PTM 215ZE devices dont work anymore.
what do I have to change in 2.0.0 to get it running? |
Beta Was this translation helpful? Give feedback.
-
I am not saying you are lying, but it's much more productive to open a new issue specifying exactly what a correct value should be (with proof) and what the actual exact full debug log output is and showing that these are different for a specific combination of devices, such that another user can indeed add their specific combination, until a pattern emerges. Once sufficient information is available or interest, a specific combination could be sent to a developer or a user might be a developer, and so on, but it starts with well written issues. |
Beta Was this translation helpful? Give feedback.
-
|
@hacscred thanks for your comment! You are right I should have been more specific. I have already placed derails of the this issue here-> Unfortunately no reaction. |
Beta Was this translation helpful? Give feedback.
-
|
@tluethi71 Commenting on an old closed ticket is not the right move. I can't debug your original issue, but the legacy triggers don't exist anymore. Use MQTT device triggers instead. |
Beta Was this translation helpful? Give feedback.
-
|
@mundschenk-at thanks for your answer. Understood. As I am not very skilled (as you might notice) I dont know how to do MQTT triggers instead..where could i get help here? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
@tluethi71 As @kennethvejen invited you, you may try to use my blueprint here. The I do not use the event entities as it is too experimental for me and it throws errors when playing with some devices on my side. |
Beta Was this translation helpful? Give feedback.
-
|
Has this "Unknown" something with the z2m 2.0.0 release to do, or is it HA ?
After "Action" on the Tap, it always returns to "Null". |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks @mundschenk-at for clearing the Button's Z2M and HA out :-) |
Beta Was this translation helpful? Give feedback.
-
|
Can someone point me in the right direction here?
I don't want to use yaml, or HA automations. How am I supposed to maintain my automations within Node RED after this legacy settings will be removed in the future? I am not really happy with being forced to do it in a certain way, I just want to still use Node Red. |
Beta Was this translation helpful? Give feedback.
-
You should ask this question to the Node Red developers. |
Beta Was this translation helpful? Give feedback.
-
|
I have just changed all my triggers from a bunch of IKEA buttons to MQTT triggers and after finding out how, it was not that difficult... Before, I used the "state node" (into the switch node to filter up/down/brightness etc. to different functions) that looked for the action sensor: Just swapped it to the "MQTT In" node:
|
Beta Was this translation helpful? Give feedback.
This comment was marked as a violation of GitHub Acceptable Use Policies
-
|
Just upgraded to 2.0.0 (Home Assistant add-on on HA 2025.1.2, Sonoff Dongle Plus E 7.4.4, 54 Zigbee devices in my network). I followed the instructions, no problems whatsoever so far. Thanks for the great work! |
Beta Was this translation helpful? Give feedback.
-
Hello, Doesn’t that make any sense at all? state is always overwritten by the device status? |
Beta Was this translation helpful? Give feedback.
-
|
Not sure what you mean, this is only about the |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, wish reading mode was on. Of course I meant the topic |
Beta Was this translation helpful? Give feedback.
-
|
Why does it matter whether that JSON key is |
Beta Was this translation helpful? Give feedback.
-
|
In FHEM you use state for the device status, regardless of the topic. That's so common. This is now overwritten by the availability topic. Now you have to map the value separately according to availability. |
Beta Was this translation helpful? Give feedback.
-
|
Well, the old topic structure was deprecated (and made a legacy feature) in 2022, so I'd say this is an FHEM issue. |
Beta Was this translation helpful? Give feedback.
-
|
After Update to 2.x i am not able to pair any new devices. The old ones are communicating, but no new device are able to connect. |
Beta Was this translation helpful? Give feedback.
-
|
At first glance, it seems to me that all my Hue buttons and dimmer switches no longer would work due to the changes of the legacy functions. Without that hold features are not longer exposed in z2m. Or am I missing something here? Maybe someone can enlighten me |
Beta Was this translation helpful? Give feedback.
-
|
Your own attempt at selective screenshots show he was responding to others who were already being as abusive as you. By your own standards you would have to take his side. |
Beta Was this translation helpful? Give feedback.
-
|
😆 Hardly, he was abrasive from the off. And anyway, on that reckoning, it's entirely possible we were also responding to him! But you do you. Other's can find the comments and make their own decisions. Edit: Oh look, he's still going! Insulting the dev team again.
D3SL, Are you actually just him from a different account? Because I don't see anyone else defending such deplorable behaviour. Either there's some big conspiracy from everyone here to gang up on him or he's being a douche. Count the down votes! |
Beta Was this translation helpful? Give feedback.
-
|
@D3SL Thanks, it's comforting to see not everyone lives in crazy town. @bobmarley2021 It's normal group behavior of inferior beings. You are presumably just too young to understand group dynamics. |
Beta Was this translation helpful? Give feedback.
-
|
@baerakafubu if you add legacy_action_sensor: true to your config then all things like hue buttons should work as before. @D3SL z2m is not HA, nor is it a part from HA. I and many others use z2m without HA, so dont confuse the 2. |
Beta Was this translation helpful? Give feedback.
-
"inferior beings"... are we all like ants to you that need to be squashed? You're giving off them psycho vibes again. Edit: crazy town ants, that is |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
it works..... |
Beta Was this translation helpful? Give feedback.
-
|
Im not sure how to prepare: However in my configuraiton.yaml I find According documentation this should be the right format: |
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.
-
|
Thanks @Koenkk for the explanation! That’s great. Does it also make it more reliable and quicker to respond? I’ve been making the changes via the UI and it’s really not that hard. It’s just a copy and paste job so happy to go with what’s now recommended! You know way more than I do! 🤭 that’s not hard to be honest hahahaha. |
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.
-
|
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.
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