Just a heads up, the Ikea Zigbee bulbs are on offer and vanishing quickly to be replaced by a Matter only eco-system. Already at my local branch there are only basic WW bulbs available (2 types). A real shame as Ikea was a great source of Zigbee stuff. Would love to see some kind of USB border ...

Just a heads up, the Ikea Zigbee bulbs are on offer and vanishing quickly to be replaced by a Matter only eco-system. Already at my local branch there are only basic WW bulbs available (2 types). A real shame as Ikea was a great source of Zigbee stuff. Would love to see some kind of USB border ...

Have these been removed in the latest stable ? Eg the ability to compare dewpoints over time and find crossing points etc.

The last update was great with lots of new functionality.

This is great news. Is it able to be used with offline LLM's ?

I used it to create a python script I call my "moon-o-meter". it calculates moon brightness by using elevation, cloud cover and moon phase and updates a percentage device. I use that to inhibit my outdoor lighting when the moon is bright because it's beautiful outside with just the bright moon.

Same here.

If you can tell me how, there are many settings and it's not possible to copy and paste. Is there a config file you would like me to upload ?

I have 2 of these and they do not show this behaviour. I also use zwaveJSui.

Brilliant work, lots of devices created.

Live log analysis would be good, for spotting errors and anomalies or whatever you want and then sending "intelligent" notifications. This could also include syslog, and other logs (zwave,zigbee etc).

There are so many things ML could do although I am not sure I would let it have too much control ...

2.2 seconds is a long time when it's on the hour with all the other hourly triggers scripts etc. My system used to be unusable every hour for a lot longer than that when I had hourly backups.

That's a 100% fix, all modes functioning perfectly. Thanks a million for your work, everything else about this release works brilliantly also.

Yes I guess I was trying to be overly thorough.

However, that worked, just the number on it's own.

"auto" and "off" also worked.

Yes on 2.4.0. I just repeated this all again, stopped z2m docker, disabled the MQTT Auto Discovery hardware item in Dz, deleted all discovery topics and base topics from the broker using Mqtt Explorer. I also deleted all devices relating to the airfilter in the Dz device list.

Then I restarted the ...

Here is the mqtt payload from mqtt explorer when i set level 5 fan speed in z2m

{"air_quality":"unknown","child_lock":"UNLOCK","device_age":799097,"fan_mode":"5","fan_speed":5,"fan_state":"ON","filter_age":348328,"identify":null,"led_enable":false,"linkquality":27,"pm25":-1,"replace_filter":true ...

In the z2m logs is this

2025-06-03 22:54:04z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/starkwind airfilter', payload '{"air_quality":"unknown","child_lock":"UNLOCK","device_age":799097,[b]"fan_mode":"[object object]"[/b],"fan_speed":0,"fan_state":"ON","filter_age":348328,"identify":null,"led_enable ...

I did notice that when I change the fan speed in Domoticz, as well as turning off the fan in z2m , it also sets the mode to "--" which perhaps indicates it is sending the wrong message and the domoticz.log message is in fact from z2m.

Zigbee MQTT: Climate device invalid/unknown preset_mode ...

Perhaps remove the retained topics from your mqtt server for this device.


Thanks for your reply. I completely deleted all topics and discovery topics, still the same. Strange that setting any speed (in Domoticz) turns off the fan speed. In the zigbee2mqtt interface all is fine. Good idea though ...

If I manually on the device change speed this change is reflected in domoticz on the old original device, but if I try to effect a change from within domoticz the device turns off, no matter which speed setting I use, with the same error.

Error: Zigbee MQTT: Climate device invalid/unknown preset ...