Lost devices after updating to 1.42.0-1 Home Assistant add-on

[Koenkk]

What happened?

After upgrading to the 1.42.0-1 version of the Home Assistant add-on, people reported that they lost all their paired devices (e.g. zigbee2mqtt/hassio-zigbee2mqtt#664). We are currently investigating why this happened in zigbee2mqtt/hassio-zigbee2mqtt#649.

What to do now?

This depends on the current version you are running:

• If you are running 1.41.0-1 (or any older version), you can safely update to 1.42.0-2
• If you are running 1.42.0-1:
  • In case you did not do any manual changes (like repairing devices or moving config folder), you can safely update to 1.42.0-2
  • In case you did fix your setup on 1.42.0-1, you can update to 1.42.0-2 but after updating to 1.42.0-2, make sure to change the data_path on the add-on UI configuration to /addon_config/zigbee2mqtt

[Pferdebockwurst]

I would try and see if it works, but this already IS my data_path in 1.42.0-1. Should it be different?

[Koenkk]

@Pferdebockwurst I expect that after updating to 1.42.0-2 it changes back to /config/zigbee2mqtt, so after updating to 1.42.0-2 change it back to /addon_config/zigbee2mqtt. Could you check if that works?

[Pferdebockwurst]

Keep your fingers crossed, trying it now.

Edit: You're right. After updating from 1.42.0-1 to 1.42.0-2 my data_path config changed from /addon_config/zigbee2mqtt to /config/zigbee2mqtt. I reverted this change, so my data_path is /addon_config/zigbee2mqtt again. Started the addon, works like a charm.

[houke]

I did move my config folder for the upgrade to 1.42.0-1 and updated the data_path to /addon_config/zigbee2mqtt, everything worked fine. Just updated to 1.42.0-2, the data_path remained unchanged (it was still /addon_config/zigbee2mqtt) did a restart and everything still works fine.

[stefanuytterhoeven]

i ran version 1.41.0-1, didn't make any changes, and updated to 1.42.0-1.
The path is still /config/zigbee2mqtt
according to the message from @Koenkk , because i didn't make any changes, I can safely update to 1.42.0-2 ....
will the path be /addon_config/zigbee2mqtt after the update to 1.42.0-2 (even when it is now /config/zigbee2mqtt ) ? or still /config/zigbee2mqtt ?

[ChristianHannover]

Hi, Koenkk,
could you please clarify:
"/addon_config" (as mentioned in your statements) or "/addon_configs" (see last "s" in "configs")?
This is also in the addon-description not entirely clear. The container provided from Home Assistant OS is "addon_configs" (with s) where already other addons placed their specific files/containers.
I am using two different Zigbee-Bridges (Sonoff ZB Bridge Pro and SLZM 06 M). SLZM works, Sonoffs ZIb Bridge Pro does not.
After second try, Sonoff (correctly: the addon I am addressing the Sonoff-Bridge) shows different errors in the logs.
Either:

• Error: spawn udevadm ENOENT
• Error: No path provided and failed to auto detect path (Of course, I checked configuration.yaml and the correct path in the addon-config page)
• Error: SRSP - SYS - stackTune after 6000ms
• ...

For the Sonoffs setup I went back to the previous version not to loose devices' pairings (never get this working under 1.41.0-1/1.42.0.1 or -2)

Thanks for any support.

[Daemonentreiber]

"/addon_configs/" is the filepath, but its "/addon_config/" for the addon configuration.

[maikkoe]

Sorry if my comment is a bit confusing, wild day :D

For me, everything started after updating to 1.42.0-2 (from 1.42.0-1) with some devices went unavailable. I tried to restore a backup, but after restore nothing worked, Z2m unable to start:

[2024-12-03 20:34:25] error: zh:adapter:zstack:manager: Configuration is not consistent with adapter state/backup! [2024-12-03 20:34:25] error: zh:adapter:zstack:manager: - PAN ID: configured=6754, adapter=6754 [2024-12-03 20:34:25] error: zh:adapter:zstack:manager: - Extended PAN ID: configured=00124b00257e0890, adapter=00124b00257e0890 [2024-12-03 20:34:25] error: zh:adapter:zstack:manager: - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d [2024-12-03 20:34:25] error: zh:adapter:zstack:manager: - Channel List: configured=11, adapter=11 [2024-12-03 20:34:25] error: zh:adapter:zstack:manager: Please update configuration to prevent further issues. [2024-12-03 20:34:25] error: zh:adapter:zstack:manager: If you wish to re-commission your network, please remove coordinator backup at /config/zigbee2mqtt/coordinator_backup.json. [2024-12-03 20:34:25] error: zh:adapter:zstack:manager: Re-commissioning your network will require re-pairing of all devices! [2024-12-03 20:34:25] error: z2m: Error while starting zigbee-herdsman [2024-12-03 20:34:25] error: z2m: Failed to start zigbee [2024-12-03 20:34:25] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions [2024-12-03 20:34:25] error: z2m: Exiting... [2024-12-03 20:34:25] error: z2m: Error: startup failed - configuration-adapter mismatch - see logs above for more information

Luckily i created a backup beforehand, I'm now back with 1.42.0-2, moved the config folder to "addons_config/45df7312_zigbee2mqtt/zigbee2mqtt" and most of the network is working again.

EDIT
//ignore
But most of the devices are not reachable/controllable via HomeAssistant/MQTT but directly by Z2M.
//ignore

Entity-IDs have been updated... Therefore, after using the correct entity-id I'm able to control the devices. But some are still offline, will check if they will reconnect after power cycle / button press / ...

**Last Edit

After power cycling the offline devices, everything is working again

[bezigebever]

@Koenkk I updated before to 10.42.0-1 and didn't have any issues, also didn't chang the path.
Now just opdated to 10.42.0-2 and everything seems to run fine.
In the GUI, the data path still is /config/zigbee2mqtt
I verified with winscp, and indeed the config is still in that folder and /addon_configs/45df7312_zigbee2mqtt is empty
So what should I do ?

[stefanuytterhoeven]

I hope so. But I'll wait a bit before installing.
I've read so many 'horror' stories. (In my mind). And so many 'solutions'...
I rely heavily on z2m, so...

[bezigebever]

Everything is fine indeed, but I thought it was necessary to move the config to the new path ?

[velodromen]

I'm also awaiting the response here since I have the exact same setup. Everything works great thus far (still on 10.42.0-1) but eventually I will have to update and I want to be certain to avoid any mistakes.

[ppkstat]

I'm still on 1.41.0-1 and scared to update to either of the new versions because of what I am reading. Can someone please explain what am I supposed to do? Am I supposed to copy the folder and change the data path before or after the update? I will be doing this via SMB if it matters.

[majkers]

I'm still on 1.41.0-1 and scared to update to either of the new versions because of what I am reading. Can someone please explain what am I supposed to do? Am I supposed to copy the folder and change the data path before or after the update? I will be doing this via SMB if it matters.

#25048 (comment)

[jerricko]

I think the main problem is that many people are using Studio Code Server to copy their configs over to the new folder, but Code Server hides the database.db file in the explorer by default, so that's why the device list is empty when you set the /addon_config/zigbee2mqtt path. Once you copy over the database.db, your devices should be there.

[Pferdebockwurst]

I think one shouldn't move the files at all. This was unintentional. If you don't move the files and you update to 1.42.0-2, the configured data_path should match the location of the config files l.

[jerricko]

After re-reading the original post, I believe you're right. I think I just assumed that the folder migration was still needed (I had updated to 1.42.0-1, reverted, then updated to 1.42.0-2) but it looks like you can use either folder, as long as you point the data path to the right location.

[Dhaeyere]

I'm still getting nowhere....

[2024-12-04 00:10:48] info: z2m: Logging to console, file (filename: log.log)
[2024-12-04 00:10:48] info: z2m: Starting Zigbee2MQTT version 1.42.0 (commit #unknown)
[2024-12-04 00:10:48] info: z2m: Starting zigbee-herdsman (2.1.9)
[2024-12-04 00:10:48] warning: zh:ezsp: 'ezsp' driver is deprecated and will only remain to provide support for older firmware (pre 7.4.x). Migration to 'ember' is recommended. If using Zigbee2MQTT see #21462
[2024-12-04 00:10:48] error: zh:ezsp:ezsp: Connection attempt 1 error: Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_ca1fa0e21741ed11854d83a7ccf2b06c-if00-port0
[2024-12-04 00:10:53] error: zh:ezsp:ezsp: Connection attempt 2 error: Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_ca1fa0e21741ed11854d83a7ccf2b06c-if00-port0
[2024-12-04 00:11:03] error: zh:ezsp:ezsp: Connection attempt 3 error: Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_ca1fa0e21741ed11854d83a7ccf2b06c-if00-port0
[2024-12-04 00:11:18] error: zh:ezsp:ezsp: Connection attempt 4 error: Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_ca1fa0e21741ed11854d83a7ccf2b06c-if00-port0
[2024-12-04 00:11:18] error: z2m: Error while starting zigbee-herdsman
[2024-12-04 00:11:18] error: z2m: Failed to start zigbee
[2024-12-04 00:11:18] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-12-04 00:11:18] error: z2m: Exiting...
[2024-12-04 00:11:18] error: z2m: Error: Failure to connect
at Ezsp.connect (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:364:19)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:186:13)
at EZSPAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:152:16)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:137:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:161:27)
at start (/app/index.js:154:5)

[Pferdebockwurst]

For me this doesn't seem related to the bug mentioned in this issue. Your z2m instance is able to read the config file, because it's looking for the adapter at a certain address, which is given in the config (in your case /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_ca1fa0e21741ed11854d83a7ccf2b06c-if00-port0).

I would suggest that you check the address at which your adapter is accessible. Maybe this has changed for whatever reason.

[AXEBro]

What's weird Is I got the same adapter issue - for a different adapter. I unplugged and plugged it in, didn't work. Then I shutdown the VM, AND the hypervisor host. After that I unplugged and plugged, and then turned everything back on.

That seemed to stabilize things. My config directory is still the old one.

[rhakbari]

I am running HAOS on a rp-pi3 and My devices are being unresponsive after 5-6 hrs. I have being facing this issue in this new update. Please guide me what steps i should be taking. Thanks

[rhakbari]

No i did not move any files or edited any data_path, I just updated my addon and i started having this issue with all my zigbee devices

[maikkoe]

Same behavior as for me. I think you need to update the data path and maybe also copy the content. But I would do a backup and test it step by step.

[rhakbari]

But if the contents are in "config/zigbee2mqtt" and the data_path is also the same directory then i dont think there should be an issue. The thing is my devices are not disappearing but instead they are becoming unresponsive after like 6 hrs at least. I am unable to control their state via HA but the devices are shown in the dashboard.

[maikkoe]

But after the update Z2M requires data path to be set to '/addon_config/zigbee2mqtt'.

[maikkoe]

#25048 (comment)

[majkers]

Thanks for clarifying!. But IMHO one thing in these instructins is missing. What exactly should do people that still run 1.41.0-1 and want to update? Will the migration be done automatically? In all cases? Data_path might be different for many of us? Or maybe nothing will change for now?
Like me for example. I still run 1.41.0-1 and (don't know why) my data path is /share/zigbee2mqtt. Do I have to do something for now?

[Koenkk]

If you are running 1.41.0-1 (or any older version), you can safely update to 1.42.0-2

You can just upgrade as usual when on 1.41.0-1.

[r0bb10]

@Koenkk as already described by someone in the issue many have problems with moving the config directory and actually loosing everything paired.. this is due the people moving only the content of the zigbee2mqtt folder and not the whole directory.

the previous version had the files into /config/zigbee2mqtt (or the /homeassistant/zigbee2mqtt), so everyone is thinking to move those files in /addon_configs/45df7312_zigbee2mqtt but the container is asking for the subfolder zigbee2mqtt (according to the config tab url).

to clarify:

• if moving the content of the config dir in the /addon_configs/45df7312_zigbee2mqtt folder the addon data_path has to be set to /addon_config
• if moving the whole zigbee2mqtt folder to the /addon_configs/45df7312_zigbee2mqtt (creating so the subdirectory) the data_path can be /addon_config/zigbee2mqtt

to have it cleaner i used the first approach without the subdirectory, and everyhing just works™.

[ChristianHannover]

Halleluja, that made the trick! Thank you for this - this is the solution helped me out!

May be I did not read the instructions for updating to 1.42.0-x carefully enough, may be I misunderstood the description how to set the path correctly - for my personal opinion, dealing with different paths ("addon_configs" in HAOS files vs. "addon_config" in the addon-settings) is really confusing (at least for me) and could be better clarified.
Anyway, thank you to the developers for providing freetools (such as HAOS itself and addons like zigbee2mqtt) to steer smart homes besides the vendor's clouds and for everybody here in the discussion for giving feedback to those reporting problems/issues!

[GurbEHV]

The difference between /addon_configs and /addon_config is what got me too; that could have been way clearer

[AXEBro]

i think the S is the key - I am going to foolishly attempt this.

[AXEBro]

Thank you, all! That did it - I copied my files over (as opposed to move) - and I see that the log file is now in the /addon_configs/45df7312_zigbee2mqtt/logs path is growing.

I guess I'm now properly set for that unreleased, but released change :-)

Shall I tempt fate and update my firmware so I can ditch ezsp?

[saschafuhrmann]

I had the same problems and found out that it only works if I copy the configs files via console. Copying the configs with Studio Code Server (whether files or just the content) has no effect and Z2M starts without devices. Only when I have copied it via console Z2M starts again with all devices. Possibly some permission problems.

cp -R /homeassistant/zigbee2mqtt/* /addon_configs/45df7312_zigbee2mqtt/zigbee2mqtt/

[mbrucher]

I didn't have any issue with - 1, but updated today to - 2, no issues to report as of an hour later (just in case).

[haniham]

I just updated on my ubuntu container without Homeassistant and i have 1 remaining device in the overview, the rest seems to still work via mqtt
i only ran
cd /opt/zigbee2mqtt
./update.sh
I already updated node to v22.12.0 without success
node -v v22.12.0
dunno why the log says otherwise

/opt/zigbee2mqtt# sudo journalctl -u zigbee2mqtt.service -f Dec 05 13:24:55 ubuntu-automation systemd[1]: Started zigbee2mqtt. Dec 05 13:24:55 ubuntu-automation npm[8850]: > zigbee2mqtt@1.42.0 start Dec 05 13:24:55 ubuntu-automation npm[8850]: > node index.js Dec 05 13:24:55 ubuntu-automation npm[8862]: Starting Zigbee2MQTT without watchdog. Dec 05 13:24:55 ubuntu-automation npm[8862]: Zigbee2MQTT requires node version ^18 || ^20 || ^22 || ^23, you are running v21.7.3! Dec 05 13:24:57 ubuntu-automation npm[8862]: [2024-12-05 13:24:57] info: z2m: Logging to console, file (filename: log.log) Dec 05 13:24:57 ubuntu-automation npm[8862]: [2024-12-05 13:24:57] info: z2m: Starting Zigbee2MQTT version 1.42.0 (commit #5b907f2f) Dec 05 13:24:57 ubuntu-automation npm[8862]: [2024-12-05 13:24:57] info: z2m: Starting zigbee-herdsman (2.1.9) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false} Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: zh:zstack:znp: Serialport opened Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: zigbee-herdsman started (resumed) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}' Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: SchlafzimmerMarkus/Temperatursensor (0x00124b00251cea90): SNZB-02 - SONOFF Temperature and humidity sensor (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: SchlafzimmerMarkus/Heizung (0xcc86ecfffea0fcd6): SEA801-Zigbee/SEA802-Zigbee - Saswell Thermostatic radiator valve (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: 0x00158d000183ef31 (0x00158d000183ef31): WXKG02LM_rev1 - Aqara Wireless remote switch (double rocker), 2016 model (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: 0x70b3d52b600fc846 (0x70b3d52b600fc846): BSD29_1 - Tuya Smart plug (with power monitoring by polling) (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: SchlafzimmerMarkus/Licht (0x385b44fffe6d1d2e): MS-105Z - Moes Smart Dimmer module (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: 0x00124b002513c74e (0x00124b002513c74e): SNZB-03 - SONOFF Motion sensor (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Test/DoorContact (0x00124b002513f74a): SNZB-04 - SONOFF Contact sensor (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Wohnzimmer/Button1 (0x2c1165fffe692066): HG08164 - Lidl Silvercrest smart button (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: WohnzimmerMarkus/Licht3DDrucker (0x9035eafffeaf6b83): HG06619 - Lidl Silvercrest outdoor plug (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Wohnzimmer/Button2 (0x2c1165fffe3f2711): HG08164 - Lidl Silvercrest smart button (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Unten/Wohnzimmer/TemperaturUndFeuchtigkeit (0x00124b002a51d088): SNZB-02 - SONOFF Temperature and humidity sensor (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Unten/Kueche/TemperaturUndFeuchtigkeit (0x00124b002a51c4d2): SNZB-02 - SONOFF Temperature and humidity sensor (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Wohnzimmer/Weihnachtsbaum (0xb4e3f9fffeb61ef5): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Wohnzimmer/Radio (0xcc86ecfffef675c2): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Leuchtkugel 2 (0x84ba20fffe6d3664): HG08131C - Lidl Livarno Home outdoor E27 bulb in set with flare (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Leuchtkugel (0x84ba20fffe8487db): HG08131C - Lidl Livarno Home outdoor E27 bulb in set with flare (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: 0x04cd15fffee03728 (0x04cd15fffee03728): 14156506L - Lidl Livarno Lux smart LED mood light (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Smart Outdoor Garden Lamps 2 (0xa4c138ec4aa8df27): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Smart Outdoor Garden Lamps 3 (0xa4c1382cb23cc2fe): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Smart Outdoor Garden Lamps 5 (0xa4c13853a9ee8307): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Smart Outdoor Garden Lamps 4 (0xa4c1388a28c9b6a1): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Smart Outdoor Garden Lamps 1 (0xa4c1381c99fd6e4c): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Garten/Leuchtkugel3 (0x84ba20fffe743691): HG08131C - Lidl Livarno Home outdoor E27 bulb in set with flare (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: verstärker garten (0xec1bbdfffe9d1d49): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Gartenlampe (0x9035eafffe5ace00): HG07834C/HG08131C - Lidl Livarno Home E27 bulb RGB+CCT (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: RepeaterPA1 (0x00124b00095977ac): CC2530.ROUTER - Custom devices (DiY) CC2530 router (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Unten/Wohnzimmer/WeihnachtsbeleuchtungHinten (0xcc86ecfffefa7388): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Unten/Wohnzimmer/Weihnachtsschalter (0x2c1165fffe99b01e): HG08164 - Lidl Silvercrest smart button (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Unten/Schlafzimmer/TemperaturUndFeuchtigkeit (0x00124b002a4ee834): SNZB-02 - SONOFF Temperature and humidity sensor (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: 0xa4c138b1e910b119 (0xa4c138b1e910b119): TS0601_soil_3 - Tuya Soil sensor (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Keller/Heizung/HeizstabPower (0xe0798dfffedabbc0): EAKCB-T-M-Z - EARU Smart circuit breaker (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: 0xa4c1388e98e1b39e (0xa4c1388e98e1b39e): TS0044 - Tuya Wireless switch with 4 buttons (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: 0xa4c13889a37e8994 (0xa4c13889a37e8994): ZG-101ZL - Loginovo Smart button (EndDevice) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Oben/Wohnzimmer/Licht (0x4c5bb3fffe12cae4): MS-104BZ - Moes Smart light switch module (2 gang) (Router) Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Currently 34 devices are joined. Dec 05 13:24:58 ubuntu-automation npm[8862]: [2024-12-05 13:24:58] info: z2m: Zigbee: disabling joining new devices. Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m: Connecting to MQTT server at mqtt://localhost Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m: Connected to MQTT server Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}' Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m: Started frontend on port 888 Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SchlafzimmerMarkus/Temperatursensor', payload '{"battery":48,"humidity":46.9,"linkquality":75,"temperature":22.82,"voltage":2800}' Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SchlafzimmerMarkus/Heizung', payload '{"anti_scaling":"ON","away_mode":"OFF","battery_low":false,"child_lock":"UNLOCK","current_heating_setpoint":23,"frost_detection":"ON","linkquality":78,"local_temperature":21.3,"local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"ON"}' Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x00158d000183ef31', payload '{"battery":100,"device_temperature":25,"linkquality":51,"power_outage_count":87,"voltage":3025}' Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x70b3d52b600fc846', payload '{"current":0,"energy":0,"linkquality":66,"power":0,"state":"ON","voltage":227}' Dec 05 13:24:59 ubuntu-automation npm[8862]: [2024-12-05 13:24:59] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SchlafzimmerMarkus/Licht', payload '{"brightness":128,"light_type":"led","linkquality":78,"min_brightness":2,"power_on_behavior":"on","state":"OFF"}'

[haniham]

in my config.yaml i needed to change

frontend: port: 888

to
frontend: port: 8181
or default works too
frontend: port: 8080

Port 777 works too

When i try anytime port 888 only shows 1 device reproduceably in the web ui

Why, i dunno - is this related to the homeassistant iussue, i dunno

[grant17]

Hello, hoping someone might be able to help me with an issue I have been having with the latest update to 1.42.0-2

I am currently running version 1.41.0-1 and have no issues, when installing version 1.42.0-2 I get issues with my Zigbee groups, mainly the ones that are also bind directly with an Ikea rodret remote.

When trying to switch the group from Home Assistant i get the following error:

2024-12-06 13:47:27] error: z2m: No converter available for 'state' ("OFF")
[2024-12-06 13:47:31] error: z2m: Failed to poll onOff from Summer House Dimmer 2 (ZCL command 0xa4c138f181a00306/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (60) Error: waiting for response TIMEOUT))

I am running Home Assistant in a VM on ESXI, I have rolled back and all works ok again but wanted to understand what’s wrong as I like to keep the system up to date.

Many Thanks

[zawnk]

I've noticed very similar issues the last couple of weeks but I haven't tackled them yet. But I also haven't updated the addon for a while, so I don't think this issue is related to 1.42.0 (I'm still running 1.41.0-1).

I'm also using also Ikea switches (but the old E1743) and over the last couple of weeks they just don't turn lights on anymore (or only turn some of the lights on they're supposed to turn on). It also causes a confusing state of the lamps in HA with them either being shown on or off, but to turn them off via HA, I have to turn them on and then off again. As I said, I haven't messed with them yet because I won't be at home for a few weeks, so I didn't want to touch it yet, so not sure if I will get the same 'no converter available' error when I try to unbind and bind them again.

But I have this behaviour also on 1.41.0-1.

[aplawson7707]

Following the breadcrumbs on this issue led me to this discussion thread and if you're in my weird edge-case hopefully you'll run into this thread, too.

I have just one small thing to add for people experiencing this issue with a fresh, first time install of Zigbee2MQTT v.1.42.0-2 AND switching to the Sonoff 3.0 USB Dongle Plus for the first time (I know, I picked a heck of a week to migrate from Deconz and Conbee II to Z2M and a Sonoff).

---

TL;DR - You may need to manually enter a "serial" entry in your /addon_configs/45df7312_zigbee2mqtt/zigbee2mqtt/configuration.yaml file after following the above steps and relocating your config/zigbee2mqtt directory to the right place.

---

Step 1: Follow the prescribed fix of manually moving the /config/zigbee2mqtt directory and contents to the /root/addon_configs/45df7312_zigbee2mqtt directory

Step 2: Navigate to Settings > Add-Ons > Zigbee2MQTT > Configuration and set the data_path to /addon_config/zigbee2mqtt

(Note: that directory is specifically spelled "addon_config". There is no "s" at the end of addon_config. I see that confusing some people.)

Step 3: This was the missing piece for my specific edge-case. Using the File Editor add-on, I opened /addon_configs/45df7312_zigbee2mqtt/zigbee2mqtt/configuration.yaml and manually entered the following entry:

serial:
  port: >-
    /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_06f9d1305855ef11a61c5973cc32aab1-if00-port0
  adapter: zstack

(Note: Your actual serial data may be different from mine - it depends on your hardware. If you're using USB hardware you can open the Terminal add-on, navigate to your home directory with $ cd ~ and then run $ ls /dev/serial/by-id/ to find your hardware's address.)

The Add-On UI does offer a place to enter the serial data for your zigbee coordinator but the add-on was unable to start zigbee-herdsman even if I put the serial data in that UI "serial" section. After several unsuccessful attempts to diagnose the issue, I noticed that my configuration file didn't match some of the posted working configuration files of other users in one key way: my config file had no serial data in place despite populating that "serial" field in the UI. On a whim, I manually entered that data into my config file and started the add-on successfully. I have been able to successfully introduce new devices to my Z2M instance and all is well.

Hope this helps somebody!

[inomdzhon]

Thank you 🙏

(Note: that directory is specifically spelled "addon_config". There is no "s" at the end of addon_config. I see that confusing some people.)

Really! It's confusing...

[Pauligrinder]

I had a similar issue when migrating my zigbee2mqtt installation (not hass addon) to another computer. I was previously running version 1.33 on Arch Linux ARM, and now migrated to a machine running Debian Bookworm and zigbee2mqtt version 1.42.0 (since unlike Arch, Debian does not have zigbee2mqtt in its' repo, so I had to install manually from git).

What solved it for me was doing incremental updates: 1.33 -> 1.36 -> 1.39 -> 1.42. And now I'm on the most recent version and everything seems to be working. In order to do this, the depth-parameter had to be removed from the git clone command so it pulls the whole git-history, and then I checked out the specific commit for each version before doing npm ci && npm run build.