2.1.0

[Koenkk]

Feel free to discuss the 2.1.0 release here!

[autosvet22]

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?

[frkurtoglu]

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

[g-chevalier]

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?

[g-chevalier]

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!

[chrivers]

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 😅

[mundschenk-at]

Koenkk does monthly releases.

[Koenkk]

Every 1st of the month = release day.

[chrivers]

Ah, very good. I learned something today 😄

[frkurtoglu]

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