The device was created in the past and the errors appeared after updating to 2025.2 stable. I haven´t tried to recreate the device yet.

Thank u so much for the hint! I think I´ve found the config:

{
"action_template": "{% set values = {None:None,'idle':'idle','heat':'heating','cool':'cooling','fan_only':'fan'} %}{{ values[value_json.running_state] }}",
"action_topic": "zigbee2mqtt/Kitchen",
"availability": [
{
"topic ...

I have no config topic for the devices in my zigbee2mqtt broker. Do I have to activate something specific to publish the config topic?

My Selector Switch has 3 options:
0 -off
10 -auto
20 -heat

The MQTT Explorer shows, that the selector changes the "system_mode" of the thermostat to "off", "auto" or "heat".

So my selector switch is connected to the "system_mode" of the thermostat and not to the running_state as in Hans case.

Hello together,

I have the same problem with a SONOFF TRVZB thermostat.

The error log is full of:
Error: zigbee2mqtt: Climate device invalid/unknown action mode received! (0x0cae5ffffeca00b2_climate_zigbee2mqtt: heating)

Payload shows that the running_state is "heat" instead of the, by Domoticz ...

No, there are no serial devices at all. Also nothing in ttyUSBx or ACMx.

dmesg shows the same as on the problematic environment:

usb 1-1.2: New USB device found, idVendor=03eb, idProduct=2013, bcdDevice=10.00
usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.2: Product ...

Hey Walter,

thank you for your quick reply!

I have 2 other Pi´s with Non-Docker Domoticz 2024.4 running with the same Air Quality sensors and it wasn´t necessary to use the instructions for the installation. I didn´t change the udev rules either, it just worked magically.

Hello everyone,

I´ve successfully managed to install Domoticz as a Docker container. Everything is running smoothly, except for the Voltcraft Air Quality stick.
I don´t know how to mount it in the docker-compose.yml file.
The device doesn´t show up under /dev/serial/by-id.

Under lsusb it appears ...