1.41.0

[Koenkk]

Feel free to discuss the 1.41.0 release here!

[pannal]

I don't see any devices in the frontend after the upgrade. No errors in the logs. Downgrade back to 1.40.2 works well.

[pannal]

The frontend seems to fail with index-74e84a13.js:61 WebSocket connection to 'wss://xxxxxxx/zigbee/api' failed:

[pannal]

Issue found. This is due to the new base_url setting. Z2M is behind a reverse proxy and I had this config before:

    location ^~ /zigbee/api {
        proxy_pass         http://ip:port/api;
        proxy_set_header Host $host;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

    location ^~ /zigbee {
        include snippets/proxy.conf;
        proxy_pass http://ip:port/;
    }

Now we have to set base_url to /zigbee in this case and change the NGINX config to:

    location ^~ /zigbee/api {
        proxy_pass         http://ip:port;
        proxy_set_header Host $host;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

    location ^~ /zigbee {
        include snippets/proxy.conf;
        proxy_pass http://ip:port;
    }

[KirikauKiwi]

Not able to update the Ikea Inspiring smart plugs and existing problem with Aqara DJT11LM tilt sensor not showing readings since V1.4.0 or V1.4.1

[ClasheGit]

Hello, for my case, in 1.40.1-2 the axis of my aqara DJT11LM sensors no longer goes up. So I went back to 1.40.1-1, it worked again. Now, November 1st, update 1.41.0, all of my aqara sensors work perfectly. So I did the update from 1.40.1-1 directly to 1.41.0.

[pannal]

DJT11LM works 100% in 1.41.0 for me. All readings exist and update.

[KirikauKiwi]

Thanks, I took a further look at mine and it had disconnected from the Zigbee network, so all good 👍

[PlayFaster]

Hi. The new throttle option does not appear in the UI, but I can set it, and it works, in the YAML config. Is this (not in UI yet) expected behavior?

Also, is there any intent to introduce a throttle_ignore option, similar to debounce_ignore? I think this would be very useful, on for example mmWave presence/occupancy sensors, where I would like to throttle the output from the sensor, but always (throttle_ignore) immediately publish changes to the presence attribute itself.

[RangoDzh]

I found issue:

Device type
EndDevice
Zigbee Model
SNZB-03
Zigbee Manufacturer
eWeLink
Description
Motion sensor
Support status

Supported

IEEE Address
0xa4c138662d3deda1
Network address
0xEC92 / 60562
Firmware version
0122052017
Manufacturer
SONOFF
Model
SNZB-03

After today update, this device change type to water leak sensor, and stop working, after restore backup and repair, work normal with older version of package 1.40.2-1. Please solve.

[purche42]

Same problem with lights on/off which occurs first in 1.40.2
see lights problem #24293