2.0.0

[Koenkk]

Caution

This is a BREAKING release, before updating, read #24198!

If you try to roll back to 1.x.x, make sure to also migrate back to your old data/configuration.yaml that was automatically backed up when you updated to 2.0.0.

Feel free to discuss the 2.0.0 release here!

[Danieldiazi]

Great job!

[jmcruvellier]

All good! Really important to read instructions before upgrading. Good job guys!

[kirush0280]

Trying to update:

[04-01-2025 00:41:58] debug:    z2m: Removing old log directory '/addon_config/zigbee2mqtt/log/2025-01-04.00-36-32'
[04-01-2025 00:41:58] info:     z2m: Logging to console (silenced), file (filename: log.log)
[04-01-2025 00:41:58] debug:    z2m: Loaded state from file /addon_config/zigbee2mqtt/state.json
[04-01-2025 00:41:58] info:     z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown)
[04-01-2025 00:41:58] debug:    z2m: sd-notify loaded
[04-01-2025 00:41:58] info:     z2m: Starting zigbee-herdsman (3.2.1)
[04-01-2025 00:41:58] debug:    z2m: Using zigbee-herdsman with settings: '"{\"network\":{\"panID\":6756,\"extendedPanID\":[221,221,221,221,221,221,221,221],\"channelList\":[15],\"networkKey\":\"HIDDEN\"},\"databasePath\":\"/addon_config/zigbee2mqtt/database.db\",\"databaseBackupPath\":\"/addon_config/zigbee2mqtt/database.db.backup\",\"backupPath\":\"/addon_config/zigbee2mqtt/coordinator_backup.json\",\"serialPort\":{\"path\":\"tcp://192.168.100.252:6638\"},\"adapter\":{\"disableLED\":false,\"transmitPower\":20}}"'
[04-01-2025 00:41:58] error:    z2m: Error while starting zigbee-herdsman
[04-01-2025 00:41:58] error:    z2m: Failed to start zigbee-herdsman
[04-01-2025 00:41:58] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[04-01-2025 00:41:58] error:    z2m: Exiting...
[04-01-2025 00:41:58] error:    z2m: Error: Cannot discover TCP adapters at this time. Specify valid 'adapter' and 'port' in your configuration.

Added

advanced:
  homeassistant_legacy_entity_attributes: false
  homeassistant_legacy_triggers: false
  legacy_api: false
  legacy_availability_payload: false

device_options: {}
changed to:

device_options:
  legacy: false

[MSL-DA]

This doesn't look right

[04-01-2025 00:41:58] info: z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown) (commit #unknown)

[Nerivec]

Seems you have:

serial:
   port: tcp://192.168.100.252:6638

add the adapter type too:

serial:
  port: tcp://192.168.100.252:6638
  adapter: WHATEVER_YOUR_ADAPTER_IS

https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html#basic-configuration

[kirush0280]

My Zigbee gateway Zigstar
Configuration was:

serial:
  port: tcp://192.168.100.252:6638

changed to:

serial:
    adapter: zstack
    port: 'tcp://192.168.100.252:6638'

And its works now.
I did usual upgrade through Home Assistant, I don't know why there is no commit number. I will try upgrade one more time and will check it when will next update. Thanks, I hope my change somebody helps.

[hexonMD]

This worked for me

[Blcktape]

Upgraded and all working fine without any needed chanches to config files.
Edit: My setup is fairly straight forward and not complex by design so i didnt need to do any changes.

[deveylder]

All hue taps are not working anymore. Needed to revert back to old version

[Bloodhoundje]

All hue taps are not working anymore. Needed to revert back to old version

Same issue here. The ".action" attribute has dissappeared in the homeassistant attributes (does shown them directly inside Zigbee2MQTT).

[kirush0280]

read #24198

[leonidostrovski]

Looks all types of press buttons stop to work.
Solved after adding:
homeassistant:
legacy_action_sensor: true
(source: https://github.com/Koenkk/zigbee2mqtt/discussions/24198 )

[buz-ch]

I stumbled on another breaking change which I did not see listed:

- Device icon of 'LR-Signe' should start with 'device_icons/', got 'data:image/

which is a bit unfortunate because those were put there by z2m a week ago when I clicked the respective button. Either way, glad tgo have it out again. 2.0 now properly puts paths there, BTW.

Happy new year in any case!

[thesebastianf]

same where do I edit this?

[chris-1243]

Check #25299

[kosteck]

In your devices.yml file under zigbee2mqtt find all entries referenced to in the error message, eg. the LR-Signe:

'0x...(your devide id)':
  friendly_name: LR-Signe (your device name)
  icon: '...'

Then just remove the problematic icon line, save the file (as usual I suggest making its backup first) and restart Zigbee2MQTT.
Lack of icon line should just revert to a default icon.

[RubenKelevra]

@Koenkk I think the How to get prepared? section should include the adapter: xyz setting most people need to add to their add-on config.

[sfok]

Thank you very much for the support.
I would like to note that in the upgraded version 2.0.0-1
the buttons Xiaomi Model: WXKG01LM do not work.
Please in the next upgrade, if possible, fix the above.
Thank you
Regards
Happy New Year to everyone !!!

[jmcruvellier]

LQI in map is wrong for some devices. For example it is set to 0 for one switch while in the device state it is set to 132.

[Metzlmane]

upgraded without problems, just changed the config options, started the container and it worked

i only have one problem now, that every OTA update fails, anyone else?
It might be related to my strange rootless docker setup, but previously i had no problems with any device

info 2025-01-04 16:52:20z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{},"error":"Update of 'power_work_03' failed (fetch failed)","status":"error","transaction":"f23h1-1"}'
error 2025-01-04 16:52:20z2m: Update of 'power_work_03' failed (fetch failed)

[aizmob]

upgrade failed :(

[21:05:01] INFO: �[32mPreparing to start...�[0m
[21:05:01] INFO: �[32mSocat not enabled�[0m
[21:05:01] INFO: �[32mStarting Zigbee2MQTT...�[0m
Starting Zigbee2MQTT without watchdog.
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  (0, node_assert_1.default)(result instanceof Object)

    at read (/app/lib/util/yaml.ts:24:15)
    at Object.readIfExists (/app/lib/util/yaml.ts:36:34)
    at readDevicesOrGroups (/app/lib/util/settings.ts:317:38)
    at read (/app/lib/util/settings.ts:325:5)
    at getPersistedSettings (/app/lib/util/settings.ts:393:21)
    at Object.reRead (/app/lib/util/settings.ts:640:5)
    at start (/app/index.js:130:14)
[21:07:27] INFO: �[32mPreparing to start...�[0m
[21:07:27] INFO: �[32mSocat not enabled�[0m
[21:07:27] INFO: �[32mStarting Zigbee2MQTT...�[0m
Starting Zigbee2MQTT without watchdog.
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

Restore from backup, double check prerequisites, upgrade again. No luck.
Came back to v1.42.0-2

My system is: HAOS v14.1 (latest), core v2025.1.0 (latest)
All *legacy configfile entries are set to false

[djurny]

Hi @aizmob,
IIWY, I would try commenting out groups: and then devices: from your configuration.yaml and see which one might be causing some issues.
Even though I seem to have mixed up yaml.load() in yaml.ts::read() and state.ts::load(), the log_level: debug output of a bad run would be great.
Thx,
Groetjes,

[aizmob]

Thanks a lot, bro!
Lets wait for a new update to get that "bad run" again.

[djurny]

Hi @aizmob,
I have a suspicion that the empty groups.yaml file is triggering the assert(result instanceof Object) in yaml.ts::read() (added by 6f6e7c3 due to #24357), but let's wait for your feedback.
Groetjes,

[aizmob]

ok, thank You!

[aizmob]

Hi @djurny !

I have a suspicion that the empty groups.yaml file...

Yes!!! Commented out config-file entry after unsuccessful add-on update to v2.0.0-2 and z2m was started. Everything (except few illumination_lux entities) works fine.
thanks a lot!

[foglietti]

I have created blueprints for Xiaomi Mi WXKG01LM and Aqara WXKG02LM_rev2 working with Zigbee2MQTT 2.0.0-1.

WXKG01LM

WXKG02LM_rev2

[irekzielinski]

Trying to migrate to 2.0 by adjusting configuration first. Noticed that setting this:
legacy_availability_payload: false

will make all my devices in Home Assistant unavailable. Tried re-loading of MQTT integration, no improvement.
Any tips? Thank you!

[chris-1243]

I am glad to have spend some time last month to get prepared. It went like an usual update and really smoothly.

[ashishgururani]

Do you just try and see what breaks? Or is there another easier option. My setup is simple - ha os, no docker or VM and using the SkyCoonect stick. 15 AliExpress Tuya sensors/sockets.

[aizmob]

Shall wait. For "another easier option".
The best way I see now is to fully reinstall the add-on :(

[AverageJoe89]

Next time, would be possible to include information about breaking changes into HA pre-update window? Get inspired by Node Red for example, it would avoid plenty of unnecessary defects open.

[Koenkk]

Is #24198 what you mean?

[fabricepipart]

I am a software developer and I think I understand the frustration of both sides.

@Koenkk
As a software developer, I clearly understand that some proper effort was put in place to do a pre release, test and document the migration process. Thanks for that.

@AverageJoe89
But as a Home Assistant user, honestly I got caught by the major release too. And I lost one day trying to recover everything ... One day is what I spend... every year ... on my home automation maintenance...

I had set auto update. And the issues is that I saw no warning whatsoever with my regular usage of Home Assistant. I admit that the auto update was a bit dangerous. Maybe that should not auto update to a major... But the annoying part is that now, when Home Assistant deprecates a config or prepares for a major change, you get a warning that you clearly see in the UI next to the Setting icon. Any similar mechanism catching the attention of the average user would be very welcome!

[assensus]

Hi Koenkk and all other contributors,
I wanted to give you a big compliment! The installation and conversion to version 2.0 worked without any problems for me on a Raspbi 4. Providing such massive changes in this quality is an achievement that deserves the highest recognition.
Thank you for your work and Happy New Year,
Reiner

[buz-ch]

Thanks fixing was easy enough, mostly posted it in case someone else gets stuck

…

On Sun, Jan 5, 2025, 12:52 kosteck ***@***.***> wrote: In your devices.yml file under zigbee2mqtt find all entries referenced to in the error message, eg. the LR-Signe: '0x...(your devide id)': friendly_name: LR-Signe icon: '...' Then just remove the problematic icon line, save the file (as usual I suggest making its backup first) and restart Zigbee2MQTT. Lack of icon line should just revert to a default icon. — Reply to this email directly, view it on GitHub <#25440 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJIIPU4C3N7GYVJV7NCWCGD2JEMGXAVCNFSM6AAAAABUSKGSKCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZTHA4DOMY> . You are receiving this because you commented.Message ID: ***@***.***>

[itavero]

FYI: If you are using homebridge-z2m, please update to the latest beta version (homebridge-z2m@next) if you experience issues with Zigbee2MQTT v2.0.0

[neneonline]

Everything has stopped working for me today... not sure if it is related to this update.

Trying to troubleshoot things... I have updated my Sonoff Dongle to 7.4.4, changed adapter to "ember". I don't seem to see errors in the log... but lights and switches are not working... and whenever I try to go to to the Zigbee2MQTT menu I get a "502: Bad Gateway" error.

Pasting here the log just in case someone can see anything strange:

[23:21:21] INFO: Preparing to start...
[23:21:21] INFO: Socat not enabled
[23:21:22] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-01-05 23:21:32] info: 	z2m: Logging to console, file (filename: log.log)
[2025-01-05 23:21:32] info: 	z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown)
[2025-01-05 23:21:32] info: 	z2m: Starting zigbee-herdsman (3.2.1)
[2025-01-05 23:21:33] info: 	zh:ember: Using default stack config.
[2025-01-05 23:21:33] info: 	zh:ember: ======== Ember Adapter Starting ========
[2025-01-05 23:21:33] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-01-05 23:21:33] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-01-05 23:21:33] info: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-01-05 23:21:33] info: 	zh:ember:uart:ash: Serial port opened
[2025-01-05 23:21:33] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-01-05 23:21:34] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2025-01-05 23:21:34] info: 	zh:ember:uart:ash: ======== ASH started ========
[2025-01-05 23:21:34] info: 	zh:ember:ezsp: ======== EZSP started ========
[2025-01-05 23:21:34] info: 	zh:ember: Adapter EZSP protocol version (13) lower than Host. Switched.
[2025-01-05 23:21:34] info: 	zh:ember: Adapter version info: {"ezsp":13,"revision":"7.4.4 [GA]","build":0,"major":7,"minor":4,"patch":4,"special":0,"type":170}
[2025-01-05 23:21:34] info: 	zh:ember: [STACK STATUS] Network up.
[2025-01-05 23:21:34] info: 	zh:ember: [INIT TC] Adapter network matches config.
[2025-01-05 23:21:34] info: 	zh:ember: [CONCENTRATOR] Started source route discovery. 1248ms until next broadcast.
[2025-01-05 23:21:34] info: 	z2m: zigbee-herdsman started (resumed)
[2025-01-05 23:21:34] info: 	z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":4,"patch":4,"revision":"7.4.4 [GA]","special":0,"type":170},"type":"EmberZNet"}'
[2025-01-05 23:21:34] info: 	z2m: Trådfri Cocina (0x90ab96fffebbd99a): ICPSHC24-30EU-IL-1/ICPSHC24-10EU-IL-2 - IKEA TRADFRI LED driver, 30 w (Router)
[2025-01-05 23:21:34] info: 	z2m: Styrbar Botón Cocina (0x287681fffefc242b): E2001/E2002 - IKEA STYRBAR remote control (EndDevice)
[2025-01-05 23:21:34] info: 	z2m: Kitchen Light 03 (0xa4c1386ee70f598f): ZB-TD5-RCW-GU10 - Moes RGB+CCT 4.7W GU10 LED bulb (Router)
[2025-01-05 23:21:34] info: 	z2m: Kitchen Light 04 (0xa4c1381ce251d648): ZB-TD5-RCW-GU10 - Moes RGB+CCT 4.7W GU10 LED bulb (Router)
[2025-01-05 23:21:34] info: 	z2m: Kitchen Light 05 (0xa4c138816c62a29f): ZB-TD5-RCW-GU10 - Moes RGB+CCT 4.7W GU10 LED bulb (Router)
[2025-01-05 23:21:34] info: 	z2m: Kitchen Light 06 (0xa4c1386ff1382b9a): ZB-TD5-RCW-GU10 - Moes RGB+CCT 4.7W GU10 LED bulb (Router)
[2025-01-05 23:21:34] info: 	z2m: Kitchen Light 07 (0xa4c138e895dd50f9): ZB-TD5-RCW-GU10 - Moes RGB+CCT 4.7W GU10 LED bulb (Router)
[2025-01-05 23:21:34] info: 	z2m: 0x142d41fffe4c1fc9 (0x142d41fffe4c1fc9): 014G2461 - Danfoss Ally thermostat (EndDevice)
[2025-01-05 23:21:34] info: 	z2m: Currently 8 devices are joined.
[2025-01-05 23:21:34] info: 	z2m: Connecting to MQTT server at mqtt://core-mosquitto:1883
[2025-01-05 23:21:35] info: 	z2m: Connected to MQTT server
[2025-01-05 23:21:35] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'

Let me also paste my configuration.yaml

homeassistant:
  enabled: true
mqtt:
  server: mqtt://core-mosquitto:1883
  user: # Here I have the username
  password: # Here I have the password
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230220084405-if00
  adapter: ember
frontend:
  enabled: true
  port: 8099
advanced:
  log_level: info
  homeassistant_legacy_entity_attributes: false
  homeassistant_legacy_triggers: false
  legacy_api: false
  legacy_availability_payload: false
device_options:
  legacy: false
devices:

# Here I have a bunch of devices

ota: {}
groups:

# Here I have some groups

version: 4

[Nerivec]

From your logs, everything appears to be in order.
Have you tried restarting your HA machine (full restart)?

[neneonline]

Yes... I have restarted it multiple times... even power cycled it multiple times :(

[neneonline]

Solved: Let me share how I solved it.

I basically had to remove all the zigbee2mqtt configuration as per this message from 2022 and reconfigure all the lights, scenes, etc. again:

https://community.home-assistant.io/t/zigbee2mqtt-502-bad-gateway-solved/447571/8

The key question is... what caused zigbee2mqtt to go crazy?

Might it have been that it updated to Zigbee 2.0.0 and it required me to update from EZSP to Ember... and somehow that changed the Zigbee network naming?

[aizmob]

z2m add-on update to v2 offer disappeared from my HA today.
So, we are waiting for less "breaking" one ;)

[aizmob]

A second try, add-on version 2.0.0-2 now.
No luck again.

But!
Now I had some info from this post from @djurny:

Hi @aizmob, I have a suspicion that the empty groups.yaml file is triggering the assert(result instanceof Object) in yaml.ts::read() (added by 6f6e7c3 due to #24357), but let's wait for your feedback. Groetjes,

And YES it was helpfull
Commented out the folowing line in my configuration.yaml:
groups: groups.yaml

and z2m v2 started successfully!

[djurny]

Hi @aizmob,
Might be good to add that the groups.yaml from your configuration.yaml was empty.

At this moment (version 2.0.0), using empty files for either devices: file.yaml or groups: file.yaml will trigger an assert() and prevent z2m from starting.

Groetjes,

[tmazza79]

Hi, I have installed z2m on a raspi zero2w board. I got the 2.0.0 release. I like how it looks like!
I have a problem with a gledopto GL-C-008P controller which I removed from another zigbee network (version 1.30.3) running on a raspi 4 and connected to the new one. The controller started misbehaving, with the color temperature slide affecting the brightness, such that sliding towards cold dims the light. it looks like the cold white does not work. It is a similar issue as depicted here #21988, yet I am not sure it's a firmware issue on my side: I have another gledopto controller, same model, same firmware, running on the other zigbee (old version) and the behaviour is normal. Maybe it's a compatibility between the firmware and the new z2m version? thanks for any help!