Zigbee2mqtt. upgrade to 2.0.0-1 not working. Have no idea why

1

Hi
Again, I took a STUPID Risk and updated zigbee2mqtt to 2.0.0-1. I wish people would stop making these breaking changes, which essentially brick my entire system.

I note there is a very brief and terse ‘prep’ bit here: Release 2.0.0 · Koenkk/zigbee2mqtt · GitHub

but did this an its still failing. Can anyone shed any light on this please?
Starting Zigbee2MQTT without watchdog.
[2025-01-04 18:01:29] info: z2m: Logging to console, file (filename: log.log)
[2025-01-04 18:01:29] info: z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown)
[2025-01-04 18:01:29] info: z2m: Starting zigbee-herdsman (3.2.1)
[2025-01-04 18:01:30] error: z2m: Error while starting zigbee-herdsman
[2025-01-04 18:01:30] error: z2m: Failed to start zigbee-herdsman
[2025-01-04 18:01:30] error: z2m: Check Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT for possible solutions
[2025-01-04 18:01:30] error: z2m: Exiting…
[2025-01-04 18:01:30] error: z2m: Error: Adapter ‘auto’ does not exists, possible options: deconz, ember, ezsp, zstack, zboss, zigate
at Function.create (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/adapter.ts:80:19)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:132:24)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:142:13)
at start (/app/index.js:161:5)

==edit== am trying to roll back to when things actually worked. I cant for the life of me now find out how to restore from backup. Anyone know?

2

This may help you

3

thanks.
Is there a “this is going to hurt, here’s a walkthrough guide” anywhere? Specifically, it looks like folk will struggle with adapters. Mine is a zig-a-zig-ah! CC2652R based adapter.

I managed to roll back, but this isn’t the answer. I am going to have to bite the 2.0.0.1 bullet sometime.

My installation has been rock solid for a couple of years now. Have now moved on from the fiddling phase, to ‘enjoying it’ phase. and have forgotten pretty much everything I learned!

4

It is never ending story. It is a curse and the bless the same time. Fortunately for me this update went smooth. The only thing I noticed is that they changed settings for lux so lux settings on esphome devices was disabled. I enabled it, changed automations to new entitiy and that was it.

And i did need to ssh to my server and run docker compose up -d to get everything working.

5

I had an issue this morning after the new update but after I added this - adapter: zstack in the configuration of the Zigbee2MQTT addon and restarted the addon everythings worked perfectly and as before.

image
image1080×1156 37.2 KB

5 Likes
6

Thank’s. That work.

7

Thanks, that worked for me.

8

Z2m 2 config change

9

Mine broke as well overnight, this worked for me

10

Lifesaver! Another thank you from me for the “adapter:” tip. Woke up this morning to falling snow and no heating after the update.

11

Very useful, thanks.

Its still more than irritating they leave some people in an absolute mess, having to trawl through thankful clues offered by people such as yourself, to get stuff working again. There seems to be no thought around risk.
==edit== updated. All seems ok now, apart from one or two entities not playing well in NR.