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
1 Like
I’m still not sure why that happens. A restart shouldn’t be required. It happened to me too. 
Hello everyone, i also have an issue after updating to version 2.0. I have several Livolo Zigbee light switches which were working fine and now they’re not working anymore. I attached my config from z2m and the error i get. I am using a sonoff zigbee dongle e and i flashed it today to Ember 7.4.5.0.
Please advise me what can i do, thank you
data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: “-d -d”
log: false
mqtt:
server: mqtt://core-mosquitto:1883
user: myuser
password: mypass
serial:
port: >-
/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_9e53e3855fe7ed1192d1626262c613ac-if00-port0
adapter: ember
baudrate: 115200
rtscts: false
Maybe you are affected by the Livolo is a bunch of junk problem. See [Feature request]: Possibility to bring back the "Permit Join forever" option · Issue #25626 · Koenkk/zigbee2mqtt · GitHub
If so either
-
Make an automation that puts Zigbee2MQTT in permit join at the same rate as it expires. Hack, ugly. Bug should help if this is your problem
-
Which is provoking and almost arrogant but truly what I personally would do. Buy new devices and smash the old junk with a hammer. If a device requires a permanent permit-join it is naughty and deserves to be punished and discarded. Life is too short for junk
1 Like
I am having an issue with adding new devices after this upgrade. They are just not found after I press the pairing button on the new device to be added. I have an old version of HA on a ssd which I replaced in my NUC and have no issue with adding the devices there, so this suggests my issue is also with the upgrade.
Has anybody else had the problem with pairing new devices or old devices that had been removed. If so did you get it resolved and how?
PS Did make the changes to configuration outlined in earlier posts here.
to anybody with these problems…
upload an old backup… restore only the zigbee2mqtt… and that’s enough to get back all working
Have only 10 days of backups. Have restored from the oldest and still have the same issue, so need to find the reason why zigbeemqtt will now not accept any new connections. This only became apparent when I tried to add another device.Existing connections in place work fine unless I remove an attempt to add again and then they fail to be discovered…
Hello All,
I have been reading about the Z2MQTT update with fear & trepidation lol I think I know what needs to be done before the update but just wanted to run it by you for validation.
I have a Sonoff Zigbee 3.0 Dongle Plus, before the update I need to add the following to my zigbee2mqtt configuration.yaml (Some of the lines are already present)
advanced:
homeassistant_legacy_entity_attributes: false
homeassistant_legacy_triggers: false
legacy_api: false
legacy_availability_payload: false
device_options:
legacy: false
Then in the configuration section of the zigbee2mqtt add-on settings under Serial ad the following:
adapter: zstack
I will also make a HA Backup and create a snapshot of the VM that is running my Home Assistance instance before attempting this update.
Thanks in advance for any help
You’re not obliged to update.
I followed the “breaking changes” warning and documents. A lot of reading, but the guides were correct.
I do see errors in the debug logs, but maybe they were there all the time anyways.
The first week several devices got offline somehow, but didn’t leave the mesh. Re-pair solved it again.
Now it works fine without issues.
Sonoff ZDongle-E ember
I use a mixed bunch of brands:
Sonoff, Aqara, Tuya, iCasa, Ikea, Lidl (= Tuya)
Zigbee2MQTT version
2.0.0 commit: unknown
Coordinator type
EmberZNet
Coordinator revision
7.4.1 [GA]
Stats
Total 50
By device type
End devices: 26
Router: 24
By vendor
LUMI: 16
eWeLink: 8
_TZ3000_kdi2o9m6: 6
_TZ3000_gjnozsaz: 5
_TZ3000_7dcddnye: 4
IKEA of Sweden: 4
_TZ3000_1obwwnmq: 2
icasa: 1
_TZ3000_qaaysllp: 1
SONOFF: 1
_TZE284_aao3yzhs: 1
_TZE204_81yrt3lo: 1
By model
TS011F: 13
WB01: 4
TS0501A: 4
DS01: 4
lumi.sensor_motion.aq2: 4
lumi.sensor_magnet.aq2: 4
lumi.weather: 4
lumi.sensor_wleak.aq1: 4
TRADFRIbulbE14WWclear250lm: 3
TS0601: 2
ICZB-R12D: 1
TRADFRI control outlet: 1
TS0201: 1
01MINIZB: 1
I just did the update after making the changes to the configuration.yaml (I only needed to add one line) and then the adapter: zstack line to the serial section of Zigbee2MQTT configuration, performed a restart and everything appears to be working without issues. Even my map in Zigbee2MQTT looks in tact and there are no errors in the Zigbee2MQTT add-on logs.
I made a snapshot of my HA VM in ProxMox before I started and even performed another HA Backup