I guess I was confused by the name of the connected device on adabter discovery:
zh:adapter:discovery: Connected devices: [{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyUSB0","manufacturer":"Silicon Labs","serialNumber":"0001","pnpId":"usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0","vendorId":"10c4","productId":"ea60"}]
You can see there it says Silicon_Labs. Anyway now it works. Thanks!
It doesn’t really say anything on the release notes about “Auto” no longer working, but this is what I had to do to get it Zigbee2mqtt addon started again: ( I have a Sonoff adapter)
Settings → Addons → Zigbee2mqtt → Configurations → Options (on the “serial” panel ) type in
adapter: zstack
Holy shit why did they do this? All my zigbee devices stopped working which i rely on to turn on the heat in my washing room so that the water doesent freeze.
Terible bad update. Im realy angry. Evrything is down entity dosent work. Im did recover to oldest version some of the sensor cam bac some not. I did manualy egain entity, action etc dosent work.
Add the correct adapter: to your serial: config, See: Adapter settings | Zigbee2MQTT
Use the new event.xxx entities instead of sensor.xxx entities for buttons and the like, See: Home Assistant | Zigbee2MQTT
Other topics that may help:
If you want something simpler you could try ZHA instead.
Well zigbee in home assistant has never been simple, i have used zha and still use it for 1 or 2 devices.
Sorry… if you want something simpler?
I may be mad, I’m running three HA instances using two different Zigbee adapters. Both adapters stopped working after this ‘update’ and from what I see from your post even after getting the adapters running again (which I haven’t) I will need to redo entities, automations etc.
Not sure what the idea behind this ‘update’ has been.
From what I’ve understood from HA is they wanted to make things easier for users. Getting more users on the platform etc. etc. This is far from making things easier.
Are there actually any people who’s setup wasn’t broken after this ‘update’?
This is going back to the days where you had to have proper programming knowledge to get HA running. May be time to start thinking what’s been caused here.
Z2M is not a Home Assistant project. ZHA is.
Sure, mine is working perfectly after adding the three required config changes.
lol… so the strategy of HA isn’t of any interest to Z2M developers. Nice!
What’s the point of doing an ‘update’ which breaks configurations? I get it… some small changes need to be made, but this is like you’re pulling the floor away below everyone forcing to spend a lot of time which doesn’t improve anything for the user.
What.is.the.point??
It’s three simple config changes that the Z2M developers deemed necessary. I have no idea why but I’m sure they have their reasons and did not do it just to piss you off.
This (Zigbee2MQTT 2.0.0 breaking changes · Koenkk/zigbee2mqtt · Discussion #24198 · GitHub) goes some way to explain why the massive changes.
My install stopped working too. It was late at night, had one or two glasses of wine (!) and decided to ‘update’. Low and behold, cries from downstairs ‘the lights aren’t working’ forced me through hazy vision to figure this out. Impossible as there was virtually zero assist linked to this change. I reverted back to 1.4.???
I get why they changed; I would do too. My lesson: Don’t do this sort of stuff half cooked. Take time to read the instructions.
Thankfully, I took the plunge and updated. Its all working now, apart from a few entities not playing ball in NR. But that’s a relatively easy fix.
Update is relatively straightforward for me. Just adding the adapter config and modify some automations to use the new event.
Ai, as a software developer myself, I understand the need for breaking changes now and again. I don’t mind them too much, sometimes a small bit of configuration needs to change. What I find a bit harder to swallow, is that I have my HA setup set to automatically update plugins. This breaking change therefore came in automatically. It might be needed to look at that config and only do automatic updates on minor versions or something.
As a software developer aware of the occasional need for breaking changes you should have realised the inherent risk in doing that.
The reason to look for this topic though, is that my config doesn’t work at all any more. I changed adapter to zstack and can now use the various objects again through the zigbee2mqtt plugin. All of the entities are however broken, no new ones have been identified. It’s not just the sensors, all of them are broken. I don’t see any relevant issues in the z2m log any more. It looks like something broke on the MQTT → HA layer. Any idea what could be causing this?
As a software developer aware of the occasional need for breaking changes you should have realised the inherent risk in doing that.
Yeah, that may be true. One thing that can help for the future though (granted there is work involved in that) is to change this config so it works more like renovate does. There you can configure different behavior for major and minor upgrades.
Restart home assistant.
Hahaha, restarting now. I thought I did that, but that may indeed have been before I changed the adapter to zstack. 
Oké, that did the trick, thought I tried that first, but indeed: must have changed a few things after. Many thanks, @tom_l
