Secondly, this kind of response is the reason I really dislike asking for help on this forum and any other home assistant forum. Do you not think I’ve searched the various forums and post all over the internet, do not think I’ve tried numerous things to try and rectify the issue?
I’ve come on here because I’ve been unsuccessful in trying to sort the issue out myself, so the first steps I’ve taken is to say “I need help” and I posted my config to see if anyone saw anything obviously wrong with that, in case I missed it. If there is nothing wrong with it, then my next steps would be to post the log, should anyone be willing to help.
Ok, so you go to your doctor and say you don’t feel well. You then don’t expect a response of “well have you googled it and searched through books/internet!”?…No. What you’d want is for your GP to say, “ok, what’s your symptoms and I’ll see if I can help”.
Honestly the very few times I’ve posted in any HA forum, ends up being a horrible experience. No one just says “Oh I know what the issue is, I can help you with that”. They all go one the offensive and you feel like you’re not welcome there. Where has everyone’s manners gone these days. I can’t understand why someone would take time out of their day to try and make someone feel unwelcome or stupid for not having the knowledge to try and fix something that doesn’t work.
A better worded initial response for you, something like “a lot of people have been having issues since the update, can you post your logs and I may be able to help” would have been much better and maybe just maybe, we might be getting somewhere by now.
You’ve touch on not posting in the correct format, again, it’s because I don’t post very often (for obvious reasons). I just think people need to learn some manners, realise there’s different levels of knowledge within the forums and a little help goes a long way for someone like me.
I don’t know a solution to this common problem. Mine also stopped working and I saw that in the morning. I check my daily update on telegram and saw that z2m was upgraded during night. I just ssh into my server and done docker compose up -d and everything was back in business.
Check this as proposed solution. I think you have to specify adapter in z2m configuration but I’m not sure as mine was in for some time.
The answer is yes, I’ve searched many posts on various forums but every I’ve tried so far has been unsuccessful. Hence the reason for asking for help on here.
Im not sure with the recent breaking changes if my config was correct. I’m being to think maybe my sonof dongle p may need to be replaced.
If you put this search into the search engine above
tags:zigbee2mqtt after:2025-01-01
You will find that in the last 6 days over 80 posts are about Z2m, and more than 80% of them are about this subject.
I have personally touched every one of them.
Asking the same question over and over is starting to get to some of us, even me, caused by a 3rd party dropping weirdness on us. Once you get the driver talking to Z2M, you will likely experience your device triggers are gone as well.
You popping in with the same question did not provide obvious evidence that you searched at all. Please forgive us if we didn’t pick up on that but you may be shocked at how many do not search.
If you want to fix the legacy action entity problem, let me answer it before you ask.
In the Z2M UI inside the menu find the Home Assistant section and check the legacy action entities box if you see that problem.
If you have any other problems, feel free to use the search terms I provided.
BTW, this is not a doctors office, we are volunteers that like to help people, even if they are not in a good mood because their stuff is broken. Ours was broken as well… We are not paid, and we have bad days, too. Coming in here only when you have a problem and complaining about the help is not, helping.
Thank you goodenough, as the author has deleted the comments that I’ve already replied to, I’m not sure you are aware of the context of the conversation we had.
As I mentioned earlier in this thread, do you not think I’ve searched many forums for an answer? Do you not think I’ve tried numerous things I’ve found in those forums to resolve the issue? And failed by the way…. Hence the reason for posting on here.
My issues started just before the 2.0 update and I’m not sure why. As far as I’m aware, I’ve not changed anything regarding Z2M. I have since uninstalled and reinstalled the 2.0 update.
I just don’t get people’s mentality when they jump on here and have a go at other people who are struggling and have asked for help. As I said in a previous message in this thread, there’s levels to people’s knowledge on here, some have an unbelievable knowledge to this sort of stuff, others need a bit of help understanding.
I’ve not asked you personally to help, I’ve just put it out there so if anyone is willing to, then they can. Really don’t understand why you need to take 10-20 minutes out of your day to basically have a go at someone who’s tried and failed.
Pal, I don’t know your expectations, but I just posted to the very likely source of your error (that you never specified), i.e. the z2m breaking change post, told you to properly format code so that it’s readable, and asks for your logs (that you still didn’t post) for further help.
If you’re calling that “having a go”, then sorry, I’m bad at sugar coating.
What you piping up for again? I have very little expectations, I’ve already said if someone wants to help then they can. I’ve not demanded it.
We’ve already been through this. Had you come on here and replied with “can you post you config in the correct format” here’s how to do it and can you post your logs, we would have got somewhere by now. But you decided to take the complete opposite tone to begin with and you’ve deleted all your comments because you didn’t want anyone to see how stupid you looked. You got some backup now, is that why you’ve decided to pop up again?
Have you followed the steps you need to do before upgrading to 2.0? Please show the contents of your /zigbee2mqtt/configuration.yaml file and the logs from the same folder.
Good reply and with a bit of humour. Very good. I’m not able to check or do anything with it for the next couple of days, but will do as you suggested when I’m able to.
Then you probably haven’t done the steps needed. Follow those, remember to specify the correct adapter type and you will probably be fine. If not, come back with logs.
Thank you fleskefjes. The kind of reply I’d hoped for, very helpful and more importantly polite.
The config, that I posted in the “incorrect format” shows I’m using the Sonoff dongle p, so I didn’t think there was a need to highlight that information again. However in a twist to all this, I have ordered myself a SMLIGHT SLZB-06, as I have a suspicion that my Sonoff had failed. Although, stupidly, I ordered the M version thinking more power is better but after doing some research, that may not be the case.
I had to edit your post to actually see if you had the correct spacing. This is why formatting matters. You actually do have the correct spacing, so this is not your problem.
In yaml, spacing matters, when you post on the forums without formats, the spacing is removed. I highly suggest you do this in the future without derailing your own thread. The spacing is highly important for people to help you, especially when you don’t supply logs.
I also edited the post to insert proper formatting.
Also, there was a quick 1 off release yesterday that is out of the ordinary for Zigbee2MQTT that addressed a few pressings issues. One of them was related to the chosen adapter and an issue with it. You may want to update the addon to ensure you’re at the latest version before trying a different adapter choice.
I’ll preface this with - It was my fault. I bet other people had the same thoughts though.
I noticed the z2m upgrade, looked at the update notes that included “Breaking changes” and just hit install - which broke all of my Zigbee stuff.
The reason I ignored that - I didn’t understand that “Breaking Changes” meant I had to change stuff on my side so stuff didn’t break. Whenever I see “Breaking anything” I tend to ignore it because it (to me) is associated with clickbait.
I suggest changing that to something like “Fix these issues BEFORE updating or it will break your Z2M”.
Having said that, I reloaded a backup - but most of my Z2M was still broken. My reason stuff was broken is I use Zigbee Groups so I can for example bind the 5 lights in my diningroom chandelier together so when the lights come on or go off they all happen at the same time. It also makes things easier for me in regards to helpers, entities, and devices.
I didn’t expect a Z2M update to delete my zigbee groups. I did recreate them, and planned on upgrading the next day when I had time and my wife wouldn’t complain. Unfortunately the upgrade updated itself the next morning and none of our lights worked again. For the life of me, I can’t find where to turn auto update off on a single integration like Z2M. I have somewhere over 100 zigbee devices, so it was awesome fixing them twice, and regrouping them again.
I like Z2m - better support for more devices, and I like the dashboard stuff a lot. I switched from ZHA because of that. This update, however, cost me a lot of time and annoyance because the wife was complaining about the lights the whole time I was trying to fix it - and it broke the next day. Ugh.
menu find the Home Assistant section and check the legacy action entities box if you see that problem.
