2.1.0 and 2.1.1 #26104

Koenkk · 2025-02-01T20:27:03Z

Koenkk
Feb 1, 2025
Maintainer

Feel free to discuss the 2.1.0 and 2.1.1 release here!

Note that 2.1.1 is a hot-fix release primarily aimed at resolving problems with several Tuya devices not updating (e.g. #26168, #26124, #26180)

autosvet22 · 2025-02-02T06:26:55Z

autosvet22
Feb 2, 2025

Hello everyone. After updating to version 2.1.0, the positions of the "TS0601_lilistore" curtain motors are displayed incorrectly. I had to revert to the previous version. I have two of these devices, and both behave the same way. After restoring from backup, everything works fine. Has anyone encountered something similar?

1 reply

frkurtoglu Feb 3, 2025

Me too.. after updating to version tuya ts0601 does not display correctly and never update

g-chevalier · 2025-02-02T12:21:43Z

g-chevalier
Feb 2, 2025

Hello,

After migration from 2.0.0-2 to this new 2.1.0 release, my external converters file trigs an error:

[2025-02-02 11:06:53] error: 	z2m: Failed to load external converter 'GC-Corp-Devices.js'
[2025-02-02 11:06:53] error: 	z2m: Check the code for syntax error and make sure it is up to date with the current Zigbee2MQTT version.
[2025-02-02 11:06:53] error: 	z2m: External converters are not meant for long term usage, but for local testing after which a pull request should be created to add out-of-the-box support for the device
[2025-02-02 11:06:53] error: 	z2m: Failed to call 'ExternalConverters' 'start' (TypeError: Cannot read properties of undefined (reading 'options')
    at prepareDefinition (/app/node_modules/.pnpm/[email protected]/node_modules/src/index.ts:367:23)
    at addDefinition (/app/node_modules/.pnpm/[email protected]/node_modules/src/index.ts:426:18)
    at ExternalConverters.loadJS (/app/lib/extension/externalConverters.ts:49:30)
    at ExternalConverters.loadFiles (/app/lib/extension/externalJS.ts:156:24)
    at ExternalConverters.start (/app/lib/extension/externalJS.ts:45:20)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at Controller.callExtensions (/app/lib/controller.ts:368:17)
    at Controller.start (/app/lib/controller.ts:186:9)
    at start (/app/index.js:161:5))

From the error message, I don't have any clue to diagnose that.
Any idea? Some breaking changes introduced in the API? Or simply an unwanted side effect?

2 replies

g-chevalier Feb 4, 2025

After digging into the problem, I found that it is the illuminance cluster that has been removed from the converters (the "classic" one? I mean "fromZigbee.ts"). In fact illuminance disappeared, and apparently is only available now through the usage of modern extends.
I found how to refactor my code by looking into devices from custom_devices_diy.ts.

Before, I had:

    fromZigbee: [fz.on_off, fz.occupancy, fz.illuminance, fz.temperature],
    toZigbee: [tz.on_off],
    exposes: [e.switch(), e.occupancy(), e.illuminance(), e.temperature()],

Which I changed to:

    fromZigbee: [fz.on_off, fz.occupancy, fz.temperature],
    toZigbee: [tz.on_off],
    exposes: [e.switch(), e.occupancy(), e.temperature()],
    extend: [illuminance()],

It's working again.
I have now a concern: I'm afraid other clusters may disappear like that in the future.
As I could not find how to move the on/off cluster to the modern extends API, I cannot prepare my converters to a more future proof code.
Where can we find some documentation on that?

@Koenkk I believe you'll answer "External converters are not meant for long term usage, but for local testing after which a pull request…" as written in the logs, but what is the policy with DIY devices that are not from the community?

I know this is complex and the community is asking a lot to all devs… Thanks for all this work!

Koenkk Feb 5, 2025
Maintainer Author

Try to rely as much as possible in the modern extends, that should reduce the amount of breaking changes (no guarantees of course, this is not considered an official interface)

chrivers · 2025-02-02T14:55:29Z

chrivers
Feb 2, 2025

I don't know what the timeline for 2.1 is - is it "when it's ready", or is there some sort of regular(ish) cadence for these releases?

But in any case, I would really enjoy if we could fit some of the potential Philips Hue fixes and improvements in.

EDIT: Derp, I meant for the next release... these things move quickly 😅

3 replies

mundschenk-at Feb 2, 2025

Koenkk does monthly releases.

Koenkk Feb 2, 2025
Maintainer Author

Every 1st of the month = release day.

chrivers Feb 3, 2025

Ah, very good. I learned something today 😄

frkurtoglu · 2025-02-03T17:21:26Z

frkurtoglu
Feb 3, 2025

Hello everyone. After updating to version 2.1.0, the positions of the "TS0601 radiator valve are displayed incorrectly and stopped to updating.

0 replies

domeq · 2025-02-04T19:21:42Z

domeq
Feb 4, 2025

Wow, got to say this has been one of the most spectacular update fails in my history 😆

I have my entire home heating managed by a bunch of Tuya TV02-Zigbee thermostats.

After an automatic update to 2.1.0 I lost control over them either entirely or at least partially, but the result was the worst possible:
problem wasn't visible in Home Assistant or Zigbee2MQTT, but all thermostats suddenly started going full on 24/7. It took me and my family a while before we figured out why we were feeling so bad, even longer to figure out why our battle-tested thermostats are suddenly trying to cook us 🤣

Luckily it all got back to normal after a downgrade back to 2.0.0.

1 reply

domeq Feb 8, 2025

@Koenkk I tried switching to 2.1.1 to see if thermostats work fine again there - nope, still broken :(

The way I test it is I get into device's exposes tab and update Local temperature calibration (move it all the way up/down).
On 2.0.0 Local temperature right below the slider reflects my change immediately. Same thing happens in Home Assistant.
On 2.1.0 and 2.1.1 nothing happens :(

MrFrenzyyy · 2025-02-04T19:33:27Z

MrFrenzyyy
Feb 4, 2025

After updating i get an error and i cannot start zigbee2mqtt. Anyone has an idea?

[2025-02-04 17:59:35] error: z2m: Error while starting zigbee-herdsman [2025-02-04 17:59:35] error: z2m: Failed to start zigbee-herdsman [2025-02-04 17:59:35] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2025-02-04 17:59:35] error: z2m: Exiting... [2025-02-04 17:59:35] 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:670:19) at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1533: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:142:13) at start (/app/index.js:161:5)

2 replies

chris-1243 Feb 4, 2025

Check this link. It might help you to solve the issue.

https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html#error-srsp-sys-ping-after-6000ms-for-zstack-or-host-fatal-error-for-emberznet

If you may provide a debug log of the startup sequence

MrFrenzyyy Feb 5, 2025

I had to reflash my dongle to het it working again

clicks-dotcom · 2025-02-05T20:48:55Z

clicks-dotcom
Feb 5, 2025

Not sure if this is intended, but the pairing details for the BADRING water leakage sensor (E2202) from the supported devices went away with this release. I think this also applies to some other devices. Looking at the git files for pre-2.1.0 it was still there.

3 replies

Koenkk Feb 5, 2025
Maintainer Author

It's still there: https://github.com/Koenkk/zigbee-herdsman-converters/blob/3deb7bf8d7c39e5983fc27392b7bd92ac168c5ea/src/devices/ikea.ts#L931

clicks-dotcom Feb 5, 2025

Sorry about the confusion. The device is still there, but the docs appears to have changed.

Specifically, in zigbee2mqtt/docs/devices/E2202.md, the pairing section of this document was removed.

Pre:
https://github.com/Koenkk/zigbee2mqtt.io/blob/1f05aa52535e9720092d4b6cdb8ee8efcb8084a2/docs/devices/E2202.md

Post:
https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/E2202.md

Koenkk Feb 6, 2025
Maintainer Author

Not sure what happened, added it back!

AXEBro · 2025-02-06T02:46:33Z

AXEBro
Feb 6, 2025

Anyone else have issues with Illuminance values changing range? I had a sensor that used to report Illuminance in the hundreds range that went to single digits after this update.

I figured I can just compensate and adjust my automations. However after this update, it stopped reporting/refreshing the Illuminance value at all - Lux was stuck on 3, no matter how much light there was. Reverted to backup and everything went fine.

Zigbee Model: TS0225
Zigbee Manufacturer: _TZ321C_fkzihax8

Manufacturer: LeapMMW
Model: MTD085-ZB

1 reply

Koenkk Feb 6, 2025
Maintainer Author

Will be fixed in the 2.1.1 release

leewilko · 2025-02-07T17:10:21Z

leewilko
Feb 7, 2025

Hi, I have a strange problem when upgrading from 2.1.0-1 to 2.1.1-1 that all of my Mains powered Zigbee devices, mainly Ikea Zigbee repeaters but also Sonoff ZBminiL2 devices will go Offline. I am using the Zigbee Dongle P. Running on a Physical X86 host.

I can re-create this problem as I tried it twice last night upgrading from 2.1.0-1 to 2.1.1-1 will take these mains powered devices all offline. They do not re-connect. I tried power cycling one of the Ikea plug in repeaters and this stayed offline after power cycle.

I restarted Zigbee2MQTT - no change
I restarted Homeassistant -no change
Hardware rebooted Homeassistant host - no change
Powered off Homeassistant host to cut power to the dongle and powered back on - no change

I then restored HomeAssistant backup to restore back to 2.1.0-1 and the devices came back online and have stayed online.

I tried the same process again a second time repeating the above process and same results, so I can recreate this problem.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

2.1.0 and 2.1.1 #26104

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 9 comments 13 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

2.1.0 and 2.1.1 #26104

Koenkk Feb 1, 2025 Maintainer

Replies: 9 comments · 13 replies

Koenkk Feb 5, 2025 Maintainer Author

Koenkk Feb 2, 2025 Maintainer Author

Koenkk Feb 5, 2025 Maintainer Author

Koenkk Feb 6, 2025 Maintainer Author

Koenkk Feb 6, 2025 Maintainer Author

Koenkk
Feb 1, 2025
Maintainer

Replies: 9 comments 13 replies

Koenkk Feb 5, 2025
Maintainer Author

Koenkk Feb 2, 2025
Maintainer Author

Koenkk Feb 5, 2025
Maintainer Author

Koenkk Feb 6, 2025
Maintainer Author

Koenkk Feb 6, 2025
Maintainer Author