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 received ...

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. I ...

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 ...

As per title, after updating Domoticz to the latest stable from the previous I started getting these errors when I tried to change speed on the filter Error: Zigbee MQTT: Climate device invalid/unknown preset_mode received! (0x2c1165fffea5bcac_fan_zigbee2mqtt: [object object]) I had kept on an ...

This has been a blockly glitch since a few generations. Opening and closing the event and refreshing the page should fix it.

On further examination, "Set Level" also doesn't work in Blockly either, only "Open" and "Close".

I also use this device and I recently had to change a module for exactly the same device using the replace function. The new device doesn't respond to commands in dzVents and throws an error, wether using "open()" , "close()" or "setLevel(50)". 2025-05-24 14:46:31.417 Error: dzVents: There is no ...

What about installing openssl 3 on bullseye/buster ?

Be aware that with Bookworm there is a missing library (libssl?) so Domoticz needs that installed separately beforehand. I happily use zigbee2mqtt in a docker which was easy to move over so I can't help with your other question.

I remember when I started moving from Blockly to dzvents it seemed like my cpu use went up. However dzvents is much much more powerful and I found I came up against Blockly's limits pretty quickly.

Nothing in the logs but while I was asleep the solution came to me ; the newer devices needed to be added in "Set Devices" as they didn't exist when I created the remote user.

Thanks for your help Walter.

Yeah, did that and it was working before and created a test virtual device which still works. services: domoticz: image: domoticz/domoticz:stable container_name: domoticz restart: unless-stopped # Pass devices to container # devices: # - "/dev/serial/by-id/usb-0658_0200-if00-port0:/dev/ttyACM0 ...

Is there any reason new devices created on the slave aren't visible on the main Domoticz instance ? I have a previously set up test virtual switch that is working so the basic connection is fine but new devices aren't appearing. I have "allow new devices" enabled and I have tried starting and ...

Thanks walter, I managed to get something working with a python gpio2mqttAD script, still a work in progress but functional. import paho.mqtt.client as mqtt import RPi.GPIO as GPIO import time import json # GPIO setup GPIO.setmode(GPIO.BCM) GPIO.setwarnings(False) # Define relay GPIO pins (BCM ...

I have been trying to follow the GPIO guide on the wiki, however I tried installing "generic sysfs GPIO" but no devices were created. I tried using the command echo 11 > /sys/class/gpio/export but got this error -bash: echo: write error: Invalid argument At this point I tried the second method ...