1.36.1

[Koenkk]

Feel free to discuss the v1.36.1 release here!

[mundschenk-at]

@Koenkk I think there is something wrong with the auto-changelog.

[mundschenk-at]

It includes a lot of things from previous releases? E.g. origin and scenes discovery.

[Koenkk]

Ah, you mean this one. It's indeed broken until the next commit to dev

[mundschenk-at]

No I meant the one in the 1.36.1 release announcement.

[Minnozz]

Can confirm, the GitHub changelog on the new release shows the experimental Ember adapter being added, but that was in the previous release

[Koenkk]

Whoops, fixed it now.

[burmistrzak]

@Koenkk Happy release day! 💪
Great to have my improvements for the Twinguard already included, but I'll definitely have to rework that AQI <> TVOC conversion. It's unfortunately not a linear scale... 😒

[wurmi-007]

Hallo herzlichen Dank für die neue Version, kann es sein das das Dashboard nicht mehr funktioniert. Beim anklicken eines Schalters schaut es optisch aus als wäre alles ok aber beim Schalter tut sich nichts???

[wurmi-007]

Hello, thank you very much for the new version, it may be that the dashboard no longer works. When you click on a switch it looks like everything is ok but nothing happens with the switch???

[francisp2]

Previously my router-flashed Sonoff ZBBridge was supported with this external convertor

const exposes = require('zigbee-herdsman-converters/lib/exposes');
const fz = {...require('zigbee-herdsman-converters/converters/fromZigbee'), legacy: require('zigbee-herdsman-converters/lib/legacy').fromZigbee};
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;

module.exports = [
    {
        zigbeeModel: ['UT-02'],
        model: 'EFR32MG21',
        vendor: 'Custom devices (DiY)',
        description: 'EFR32MG21 Silabs Router',
        fromZigbee: [],
        toZigbee: [],
        exposes: [],
    },
    {
        zigbeeModel: ['UT-01'],
        model: 'EFR32MG21',
        vendor: 'Custom devices (DiY)',
        description: 'EFR32MG21 Zigbee Bridge Router',
        fromZigbee: [],
        toZigbee: [],
        exposes: [],
    },
];

but in 1.36.1 it is unsupported.

[mrskycriper]

@francisp2 There was a breaking change in zigbee herdsman converters 19.0.0, legacy extend no longer exists. But since it was used in external converter template, it is widely imported in a lot of them without real use.

Just remove the const extend = require('zigbee-herdsman-converters/lib/extend'); line and it will work just fine again.

[cavolo]

Hi, I try new release but have a problem with my power counter. After update the variables name changed and loose all hystory data.
For this counter use an external conversion.
I back to version 1.36.0

[wurmi-007]

Everything is known, dashboard does not function, binding is faulty!

[jamesonuk]

Seems my Hue Wall Switch modules (https://www.zigbee2mqtt.io/devices/929003017102.html#philips-929003017102) all reconfigured after installing 1.36.1 which then bound the Hue specific cluster and broke my lights.....
Took me a while to figure out what had happened as reverted back to 1.36 and 1.35 but things still weren't working. I then removed the Hue specific cluster and they worked and when I upgraded to 1.36.1 again they stopped working and Hue specific cluster was once again bound

[oneOfFiveAnd]

I also have a problem with hue wall switch modules. Didn't have the time to try solving yet, here is the most obvious error i can see. it seems that if they are configured as single push button, they now generate two actions, both with payload e.g. "left_press" with a single button push

Having said that, thanks for maintaining such a fantastic integration ... not everything can go right all the time

[oneOfFiveAnd]

addition. i have wall switches configured as due push buttons. After the version upgrade, only one of the buttons creates an activity when pushed, the other one has no effect any more. Multiple switches with same problem.

[bjornjonsson]

My wall switch modules also stopped working after the update. I use mine in a single push button configuration bound to a group. I could get them working again in 1.36.1 by:

1. Reconfigure the wall module as single push button. The update had set them back to single rocker.
2. Unbind OnOff and manuSpecificPhilips from the Coordinator. I only had PowerCfg bound to the Coordinator after this.
3. Bind OnOff and LeverCtrl to the group.

The wall switch seemed to function after the second step, so I'm not sure if the third step is necessary. I did it anyway since that is what the documentation says.

[weljajoh]

After upgrading to 1.36.1 all my Hue dimmers bound to a group no longer worked for turning on and off the lights in the group. They seem to have grown a new binding from source endpoint 1 to coordinator destination endpoint 1 during the upgrade. After removing that binding, the dimmers work again for turning lights on and off.

[JohannCR]

Can you explain how you did it ? When I try to unbind it gives me an error... But since I never used binding, not sure I did it right ^^ thx

[weljajoh]

The device needs to be awake for the unbind to succeed, so first press a button on the dimmer itself to wake it up and then click the unbind button in the Z2M GUI.

[JohannCR]

Thanks it works. Got other devices with the same coordinator bind like an Aqara SSM-U01 switch but unbinding does not work even when I hit the switch before and after... Any tip for this one ?

[JohannCR]

FYI tried this that didn't work either (please do tell if that's not correct, thanks^^):
service: mqtt.publish
data:
topic: zigbee2mqtt/bridge/request/device/unbind
payload: >-
{"clusters":["genOnOff","genDeviceTempCfg"], "from": "Inter Petit Bureau",
"to": "Coordinator"}

[JohannCR]

Nevermind, pairing again worked

[ghost]

Same what wurmi-007 has noted: dashboard does not function like in 1.36. Switches/lights cannot be controlled like in 1.36. Going to "devices", selecting the device and going to "exposes" lets control switches and lights. (on/off, dimming, changing colors, etc.). Just not in dashboard.

Nevertheless, many thanks for releasing 1.36.1. Very happy that the IKEA Water Leak Detector is supported now!

[MMi1603]

Same in my case. All device switches work as externally programmed (in my case openhab) or in the detailed device options, but not in the dashboard. When switching a device it does not show up the change in the dashboard. Strange that LQI, contacts or "last seen" are ok there, only the switches (plugs or lights) do not work.

I had used converters before (namely for the Ikea Badring), but deleted the according line in the configuration.yaml and my js-files . Maybe there is another file referring to a bad "const extend=..." as described by @mrskycriper above.

Regards,

MMi

[kamilnadzieja]

Never had any issues with the updates but here I had to revert back to 1.36.0. There is something wrong with the external converters (like they are not imported at all to z2m) plus I had many issues with the ikea devices (they were appearing as online but no data were going through). But I just want to say big thank you for your hard work and efforts!

Edit - wrong, not ikea at most but aqara/xiaomi - 70% of them went offline.

[mrskycriper]

PSA about broken external converters

There was a breaking change in zigbee herdsman converters 19.0.0, legacy extend no longer exists. But since it was used in external converter template, it is widely imported in a lot of them without real use.

Just remove the const extend = require('zigbee-herdsman-converters/lib/extend'); line from the file and it will work just fine again.

[mrskycriper]

Should I create a pull request or will it be updated by someone?

I'll add it

[Nerivec]

@mrskycriper From what I glanced, several of iluminize devices have number based or letter/text based. Might be the same thing as this with others (some currently only have text based, others only number based). Worth making a note of it 😉

[mrskycriper]

@Nerivec I'll just add this model to exiting definition for 511.050. Seems to be the same exact thing, maybe just another revision.

[cbrunnkvist]

These docs will need to be updated too: Support new devices: Extending the external definition

[mrskycriper]

These docs will need to be updated too: Support new devices: Extending the external definition

They were updated recently to remove all mentions of legacy extend

[CinciRyan]

Hello! I had to roll back to 1.36.0-1 because I lost color control of all of my Sengled E21-N1EA bulbs. In Z2M I had no option to change colors (the Color (X,Y) Field under 'Exposes'. Rolling back brings that back. https://www.zigbee2mqtt.io/devices/E21-N1EA.html#sengled-e21-n1ea

[CinciRyan]

Here's the same model bulb on a different instance running 1.36.1

[mrskycriper]

Fixed this in Koenkk/zigbee-herdsman-converters#7317 ASAP

[GustavoScramin]

Hello everyone, I was using this converter below for my lamp and fan, it is the same device. But with this latest z2mqtt update, my light bulb just disappeared, and I think z2mqtt is referencing another device. Does anyone know how I can add the lamp back? I already deleted the line of code "const extend = require('zigbee-herdsman-converters/lib/extend');"

`const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
fingerprint: [
{
modelID: 'TS0601',
manufacturerName: '_TZE200_lawxy9e2',
},
],
model: 'TS0601_fan_and_light_switch',
vendor: 'TuYa',
description: 'Fan & light switch',
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tuya.tz.datapoints],
onEvent: tuya.onEventSetTime,
configure: tuya.configureMagicPacket,
exposes: [
e.binary('status_indication', ea.STATE_SET, 'ON', 'OFF').withDescription('Light switch'),
tuya.exposes.switch(),
tuya.exposes.countdown().withValueMin(0).withValueMax(720).withUnit('m').withDescription('Max ON time in minutes'),
e.power_on_behavior(['off', 'on', 'previous']).withAccess(ea.STATE_SET),
e.enum('indicator', ea.ALL, ['off', 'off/on', 'on']).withDescription('LED indicator mode').withAccess(ea.STATE_SET),
e.numeric('fan_speed', ea.STATE_SET).withValueMin(1).withValueMax(5).withValueStep(1).withDescription('Speed of the fan'),
],
meta: {
tuyaDatapoints: [
// Datapoints from Tuya IoT platform:
//"1":"Fan switch",
//"2":"Fan countdown",
//"11":"Power-on state setting", enum. Off / On / Previous
//"12":"Indicator status setting", enum. Off / (Off/On Status) / On
//"101":"Fan Level" enum. 0 = Low, 1 = Medium, 2 = High
[1, 'state', tuya.valueConverter.onOff],
[2, 'countdown', tuya.valueConverter.countdown],
[5, 'status_indication', tuya.valueConverter.onOff],
[11, 'power_on_behavior', tuya.valueConverterBasic.lookup({'off': tuya.enum(0), 'on': tuya.enum(1), 'previous': tuya.enum(2)})],
[12, 'indicator', tuya.valueConverterBasic.lookup({'off': tuya.enum(0), 'off/on': tuya.enum(1), 'on': tuya.enum(2)})],
[101, 'fan_speed', tuya.valueConverterBasic.lookup({'1': tuya.enum(0), '2': tuya.enum(1), '3': tuya.enum(2), '4': tuya.enum(3), '5': tuya.enum(4)})],
],
},
};

module.exports = definition;`

`

[flaviocorrea13]

Hello, were you able to solve the problem? I have two fans with the same problem.

[han-alink]

Hi,
As several of my DIY devices are using the "extend" functionality, just removing this line is not enough. As an example:

{
zigbeeModel: ['SprinkCtrl'], // The model ID.
model: 'Controller for 5 sprinkler zones', 
vendor: 'Alink',
description: 'Device for the control of 5 sprinkler zones and a master valve',
extend: extend.switch(),
exposes: [e.switch().withEndpoint('l1'), e.switch().withEndpoint('l2'),
        e.switch().withEndpoint('l3'), e.switch().withEndpoint('l4'), e.switch().withEndpoint('l5'), e.switch().withEndpoint('l6')],
meta: {multiEndpoint: true},
endpoint: (device) => {
        return {l1: 1, l2: 2, l3: 3, l4: 4, l5: 5, l6: 6};    
        },
    configure: async (device, coordinatorEndpoint, logger) => {
        const overides = {min: 1, max: 3600};
        await reporting.bind(device.getEndpoint(1), coordinatorEndpoint, ['genOnOff']);
        await reporting.onOff(device.getEndpoint(1), overides);
        await reporting.bind(device.getEndpoint(2), coordinatorEndpoint, ['genOnOff']);
        await reporting.onOff(device.getEndpoint(2), overides);
        await reporting.bind(device.getEndpoint(3), coordinatorEndpoint, ['genOnOff']);
        await reporting.onOff(device.getEndpoint(3), overides);
        await reporting.bind(device.getEndpoint(4), coordinatorEndpoint, ['genOnOff']);
        await reporting.onOff(device.getEndpoint(4), overides);
        await reporting.bind(device.getEndpoint(5), coordinatorEndpoint, ['genOnOff']);
        await reporting.onOff(device.getEndpoint(5), overides);
        await reporting.bind(device.getEndpoint(6), coordinatorEndpoint, ['genOnOff']);
        await reporting.onOff(device.getEndpoint(6), overides);            
    },
},

[han-alink]

Thanks for your help. I'm still struggling with reporting. What is wrong in this device description (custom reporting values for humidity):

zigbeeModel: ['MultiSensTH'],
model: 'MultiSensTH',
vendor: 'Alink           ',
description: 'Temperature and Humidity  device',
extend: [deviceEndpoints({"endpoints":{"1":1,"2":2}}), temperature({"endpointNames":["1"]}), batteryPercentage(), 
humidity({"endpointNames":["2"]}, reporting: {min: 300, max: 60000, change: 10})],
meta: {"multiEndpoint":true}

[mrskycriper]

The meta: {"multiEndpoint":true} line is already added by deviceEndpoints modern extend.

Humidity reporting needs to be inside the same object as endpointNames

[han-alink]

Well, I have about 20 device descriptions in use for DIY devices. Updating to zigbee2mqtt release 1.36.1-1 caused almost all devices to stop working. So I reverted to 1.36.0-1 and am trying to update all device descriptions to use modernExtend. Thats is causing problems.
I changed the one I referenced in my last post. It is still not working. The temperature part (without custom reporting) works, but humidity fails.

zigbeeModel: ['MultiSensTH'],
model: 'MultiSensTH',
vendor: 'Alink           ',
description: 'Automatically generated definition',
extend: [deviceEndpoints({"endpoints":{"1":1,"2":2}}), temperature({"endpointNames":["1"]}), batteryPercentage(), humidity({"endpointNames":["2"], reporting: {min: 300, max: 60000, change: 10}})]

[mrskycriper]

Can you please create a new issue and share all external definitions there?

[han-alink]

New thread: #22150

[sanderlv]

Got an instant error after updating... made me decide to completely remove the hue wall switch...

https://community.home-assistant.io/t/z2m-rdm001-not-working-anymore-after-update-to-1-36-1-1-929003017102/713862

And in the z2m documentation for the hue wall switch https://www.zigbee2mqtt.io/devices/929003017102.html there is an error... resetting works only when pressing 10 sec and close input TWO times.

[MOROHEUZ]

Unfortunately, I also had to open an issue for Hassio
zigbee2mqtt/hassio-zigbee2mqtt#591
the Bosch Twinguards no longer updated any values.
Even a reset / relearning had no effect.

I'm also not sure whether my system has frozen as a result.
Unfortunately, I had also installed the 2024.4.1 update from HA Core.
somehow 100s of requests went out to Alexa.
also a whole lot of climate issues which all had to do with the Twinguard.

I hope the problem can be solved.
I can't do without the Twinguards.

[sam3487]

Can we use the new ember adapter now without needing to run z2m through the dev branch?

[sam3487]

Anyone got an answer to this? Thanks :)

[array81]

There is a problem with the code relating to the IMOU siren, the official code is different from the one I proposed and with this it is not possible to make the siren sound via SET MQTT (you get an error). I talk about it here.

Furthermore the siren does not have a battery so there is no point in exposing the battery.

[blakefrain]

This update seems to break commands to the deconz conbee 2

[blakefrain]

see related issue #22189