2.2.0 and 2.2.1

[Koenkk]

Feel free to discuss the 2.2.0 and 2.2.1 release here!

Note that 2.2.1 is a hot-fix release to fix various issues introduced in 2.2.0.

[Anto79-ops]

hi just updated, my devices are working fine and logs show devices alive, but dashboard shows flashing offline?

EDIT: My devices are not working, mqtt part is not updating.

EDIT 2: I rebooted the addon, and now my zigbee network is working, but still flashing offline on the dashboard.

EDIT 3: my problem is solved following these instructions: #26942 (comment)

EDIT 4: No issues to report with 2.2.1

[MBRetrofit]

Same to me, RP4 with Sonoff Ember fwr

[asedoj]

Unfortunately I am not a programmer. So I will write. Today after the update all devices have the status "unavailable". However, all devices work, the map is built normally (Tuya, z2m 2.2.0-1 )

[Anto79-ops]

Actually, my devices are not working in mqtt, only see them in the addon log.

[Mvanmierlo]

Same issue please let me know if there is something I can do (supply some logging or such)
All equipment is working, Map function also shows all connections but get the message offline at the availabilty collom.
I am running it in HA OS (latest version Core 2025.3.4) and HA OS is running as a virtual machine on Prox Mox which has its USB port directly connected (via ProxMox settings) to the HA OS host.

ttyACM0 /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___xxxxxxxxxxxxxxxxxx-xxxx

[Anto79-ops]

so its like everything is working, but nothing is working, for example:

But, I cannot turn off a switch.

[ctolzane]

Z2m 2.2.0 upgrade introduce a new revision of zigbee-herdsman-converters.
Some changes were made for Lixee device in Koenkk/zigbee-herdsman-converters#8931
The result being this error reported in the logs "z2m: Exception while calling fromZigbee converter: kwhPrecision is not defined"

[merlinpimpim]

same for me

[jonrupell]

Is there any plan to fix the connection for the Lutron Aurora's? I have 20 of them around the house literally just waiting till that gets fixed but starting to think it may soon be time to swap them out for something that still works.

[frixo3190]

same problem

[d-buschmann]

Exact same problem here

[NLand99]

Cannot run OTA Updates for Sonoff TRVZB - Update request fail

[GigiPompieru]

Do you have more than 1 device and are they all affected? I already have 1.3.0 installed so cannot test, but curious for future updates.

[NLand99]

i have 9 Devices and all are affected

[Silberfalke80]

I have 6 such devices and I have no problem - OTA can be carried out successfully - for example:

[GigiPompieru]

so it worked when they added the external temperature sensor value and it stopped working when they added hysteresis that has 1.3.0 as a requisite. donno if its related.

[GigiPompieru]

I have 6 such devices and I have no problem - OTA can be carried out successfully - for example:

checking works for me as well, I guess the issue is with actually installing the update.

[frixo3190]

All too Le mer. 2 avr. 2025, 10:27, NLand99 ***@***.***> a écrit :

…

i have 9 Devices and all are affected — Reply to this email directly, view it on GitHub <#26935 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFTRHETOPZCL4AJJZUEXGQT2XONQTAVCNFSM6AAAAAB2HU7HRSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRZG43TKNQ> . You are receiving this because you commented.Message ID: ***@***.***>

[Nardol]

Since this version Zigbee2MQTT cannot run anymore for me:

[02/04/2025 10:38:23] error: 	z2m: Could not init sd_notify: Could not locate the bindings file. Tried:
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/build/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/build/Debug/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/build/Release/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/out/Debug/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/Debug/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/out/Release/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/Release/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/build/default/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/compiled/22.14.0/linux/arm64/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/addon-build/release/install-root/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/addon-build/debug/install-root/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/addon-build/default/install-root/unix_dgram.node
 → /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/unix-dgram/lib/binding/node-v127-linux-arm64/unix_dgram.node

I run Zigbee2MQTT on ARMBian using an Odroid N2+, Linux installation method.
Using libsystemd-dev simply worked but now it looks the new used module for SystemD notify is simply not found.
I ran update.sh force to be sure with no success.

[Nerivec]

Can you try this?

pnpm i --frozen-lockfile

pnpm rebuild unix-dgram

[Koenkk]

Let's continue in #26946

[Nardol]

Can you try this?

pnpm i --frozen-lockfile

pnpm rebuild unix-dgram

I should not have downgraded and make an installation from scratch and waited for the suggestion, after a second update Zigbee2MQTT runs again.
But I keep the rebuild command if something similar happens again, thanks a lot.
Everything looks fine now, as usual 👍

[soosp]

After update all of my devices marked Offline:

If you check the avilability settings, it is unsettable:

[Koenkk]

Fixed!

Changes will be available in the dev branch in a few hours from now and in the hot fix release (will release it in the coming days)

[PiotrRaszkowski]

same here

[EcoNino]

Same here, but pay attention! it appears all is working ok. but with a Sonoff sensor the temperature showing in display is different than the one is showing in HA so it appears not updating ok. Reversed to 2.1.3-1 it backs updating ok.

[MBRetrofit]

[jimweast]

back to 2.1.3 all is good.
Wait and see

[MBRetrofit]

Meaning "try and see" more likely, yes?

[jimweast]

wait for a new version without this bug

[jmendoza221]

Jim How did you roll it back to 2.1.3?

[jimweast]

Before upgrading to the new version, I use the HA feature, which allows me to back up the current version.
Afterward, in the System menu - Backup, you can perform a restore.

[jmendoza221]

Awe ok... I wasnt able as i did not download back up phone would not allow.... Thanks for the fast response!

[Nardol]

What a fantastic version!
Cannot start the Zigbee2MQTT service anymore, can start one by hand, but by trying to fix a last time I cannot run it even by hand because network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby (Error: AREQ - ZDO - stateChangeInd after 60000ms
Just because of new sd notify management which is broken for me!

First time a version is a nightmare for me, but this first one is a big one!

[GigiPompieru]

did you try reverting to the previous version? the crap part with PanId is that you might need to re-pair your devices.

[Nardol]

I finaly succeeded in having my network again without repairing by:

1. I ensured ZB2MQTT was stopped
2. I changed the Zigbee channel
3. I started Zigbee2MQTT, by hand because issue with systemd notify
4. devices were apparently available but not possible to use
5. I stopped Zigbee2MQTT
6. I changed the Zigbee chanel to be the previously used one
7. I started, again by hand and every device were back again

I rolled back to 3.1.3, with no success until I deleted everything except config in /opt/zigbee2mqtt then reinstalled Zigbee2MQTT which now starts again using SystemD.

[darthrater78]

For comparison, I updated to 2.2.0 with no apparent issues. I am running Z2M in a docker, with MQTT in HA. I have mostly Third Reality devices, lights and plugs.

Running a coordinator UZG-01 with the XZG firmware 20240710, also a router UZG-01 with the XZG firmware 20240909

[NSJ84]

I had the same issue with all devices shown as offline. Deleted zigbee2MQTT and installed it again.

Now it won't even start the program:

[16:03:47] INFO: Preparing to start...
[16:03:47] INFO: Socat not enabled
[16:03:47] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-04-02 16:03:48] info: z2m: Logging to console, file (filename: log.log)
[2025-04-02 16:03:48] info: z2m: Starting Zigbee2MQTT version 2.2.0 (commit #unknown)
[2025-04-02 16:03:48] info: z2m: Starting zigbee-herdsman (3.4.11)
[2025-04-02 16:03:48] info: zh:ember: Using default stack config.
[2025-04-02 16:03:48] info: zh:ember: ======== Ember Adapter Starting ========
[2025-04-02 16:03:48] info: zh:ember:ezsp: ======== EZSP starting ========
[2025-04-02 16:03:48] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-04-02 16:03:48] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-04-02 16:03:48] info: zh:ember:uart:ash: Serial port opened
[2025-04-02 16:03:48] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-04-02 16:03:51] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-04-02 16:03:51] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-04-02 16:03:53] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-04-02 16:03:53] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-04-02 16:03:56] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-04-02 16:03:56] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-04-02 16:03:58] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-04-02 16:03:58] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-04-02 16:04:01] error: z2m: Error while starting zigbee-herdsman
[2025-04-02 16:04:01] error: z2m: Failed to start zigbee-herdsman
[2025-04-02 16:04:01] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-04-02 16:04:01] error: z2m: Exiting...
[2025-04-02 16:04:01] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:672:19)
at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1538:24)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:104:13)
at start (/app/index.js:149:5)

[djurny]

Upgrayedd to 2.2.0 yesterday and all is looking fine. Will check back in in a week or two.
Grt,

[malaakso]

Works well for me as well. Running in a container on rootless Podman.

[MarcR2000]

Hi,

I updated through ./update.sh as usual. However after the successful update I cannot access zigbee2mqtt through the usual IP. It's not working any more. When I roll back to previous version it recovers just fine.

error: TypeError: Module "file:///opt/zigbee2mqtt/package.json" needs an import assertion of type "json"
at new NodeError (node:internal/errors:405:5)
at validateAssertions (node:internal/modules/esm/assert:95:15)
at defaultLoad (node:internal/modules/esm/load:86:3)
at nextLoad (node:internal/modules/esm/loader:163:28)
at ESMLoader.load (node:internal/modules/esm/loader:603:26)
at ESMLoader.moduleProvider (node:internal/modules/esm/loader:457:22)
at new ModuleJob (node:internal/modules/esm/module_job:64:26)
at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:480:17)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:434:34)

What can I do?

[MarcR2000]

Updating to 2.2.1 did not solve the problem...

[GigiPompieru]

did you read the patch notes? check this out #26937

[MarcR2000]

Thank you so much! That did the trick!!!

[frixo3190]

The patch works !

[AXEBro]

Hmm- is Illuminance broken again?
My device showed stuck on 6 lx since the upgrade. I tried power cycling the device, reconfig/reinterview... no dice. Rolled back to previous version of z2m (in HA) and i'm getting a static 78 on the lux.
Zigbee Model: TS0601
Zigbee Manufacturer: _TZE204_qasjif9e
Description: Mini human breathe sensor

[Koenkk]

Should be fixed in the dev branch.

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.

[ghedolo]

update from 2.2.0 to 2.2.1
now all my sensor (7 sonoff Thermometer and 8 ikea presence) have battery and other property : null
any hints?

example follows:

example of ikea E2134
{
"battery": null,
"identify": null,
"illuminance": null,
"last_seen": "2025-04-21T21:27:08+02:00",
"linkquality": 112,
"occupancy": false,
"update": {
"installed_version": -1,
"latest_version": -1,
"state": null
}
}

example of sonoff SNZB-02P
{
"battery": null,
"humidity": null,
"last_seen": "2025-04-21T21:25:22+02:00",
"linkquality": 76,
"temperature": 18.3
}

example of sonoff SNZB-0D
{
"battery": null,
"comfort_humidity_max": null,
"comfort_humidity_min": null,
"comfort_temperature_max": null,
"comfort_temperature_min": null,
"humidity": 47,
"humidity_calibration": null,
"last_seen": "2025-04-21T21:30:06+02:00",
"linkquality": 65,
"temperature": null,
"temperature_calibration": null,
"temperature_units": null,
"update": {
"installed_version": -1,
"latest_version": -1,
"state": null
}
}

z2m/CCIB05