RGBW dimmer is not reacting on color changes

[Thaui57]

Checklist

• I am not using Home Assistant. Or: a developer has told me to come here.
• I have checked the troubleshooting section and my problem is not described there.
• I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Z-Wave JS UI version

9.21.0

ZwaveJS version

13.4.0

Describe the bug

since updating to 9.21.0 the RGBW dimmer is not reacting on color changes in Domoticz. Attached are the debug infos. On release 9.18.1 the dimmer worked well.

Quibino Flush RGBW Dimmer FW v2.98.txt

To Reproduce

color can be set in Zwave JS UI but not in Domoticz. The Zwave values does not change

Expected behavior

changing the color in Domoticz the color changes do not happen

Additional context

No response

[robertsLando]

So the discovery payload is:

"light_rgb_dimmer": {
      "type": "light",
      "object_id": "rgb_dimmer",
      "discovery_payload": {
        "state_topic": "zwave/Garderobe/38/0/currentValue",
        "command_topic": "zwave/Garderobe/38/0/targetValue/set",
        "on_command_type": "brightness",
        "state_value_template": "{{ \"OFF\" if value_json.value == 0 else \"ON\" }}",
        "brightness_value_template": "{{ value_json.value }}",
        "brightness_scale": 99,
        "rgb_command_template": "{{ {'red': red, 'green': green, 'blue': blue}|to_json }}",
        "rgb_value_template": "{{ value_json.value.red }},{{ value_json.value.green }},{{ value_json.value.blue }}",
        "supported_color_modes": [
          "rgb",
          "brightness"
        ],
        "rgb_state_topic": "zwave/Garderobe/51/0/currentColor",
        "rgb_command_topic": "zwave/Garderobe/51/0/targetColor/set",
        "brightness_state_topic": "zwave/Garderobe/38/0/currentValue",
        "brightness_command_topic": "zwave/Garderobe/38/0/targetValue/set",
        "availability": [
          {
            "payload_available": "true",
            "payload_not_available": "false",
            "topic": "zwave/Garderobe/status",
            "value_template": "{{'true' if value_json.value else 'false'}}"
          },
          {
            "topic": "zwave/_CLIENTS/ZWAVE_GATEWAY-Zwavejs2Mqtt/status",
            "value_template": "{{'online' if value_json.value else 'offline'}}"
          },
          {
            "payload_available": "true",
            "payload_not_available": "false",
            "topic": "zwave/driver/status"
          }
        ],
        "availability_mode": "all",
        "device": {
          "identifiers": [
            "zwavejs2mqtt_0xdbf01f81_node8"
          ],
          "manufacturer": "Qubino",
          "model": "Qubino Flush RGBW Dimmer (ZMNHWD)",
          "name": "Garderobe",
          "sw_version": "2.98"
        },
        "name": "Garderobe_rgb_dimmer",
        "unique_id": "zwavejs2mqtt_0xdbf01f81_8-51-0-currentColor"
      },
      "values": [
        "38-0-currentValue",
        "38-0-targetValue",
        "51-0-currentColor",
        "51-0-targetColor"
      ],
      "discoveryTopic": "light/Garderobe/rgb_dimmer/config",
      "persistent": false,
      "ignoreDiscovery": false
    }

We should compare this with the discovery payload you had in 9.18 to see if something changed that could have broke this. Also do you see any error on ZUI logs when you try to change the color?

[Thaui57]

how can I downgrade to 9.18.1

[robertsLando]

@Thaui57 Just specify 9.18 as tag. Anyway i would like to also see logs from 9.21.0 first to see what's received by zui when you try to send a color change from Domoticz

[Thaui57]

attached the log file. I seems that changes made in ZUI will send to Domoticz but the other way round there is no change in ZUI
z-ui_2024-10-08.log

[robertsLando]

Seems the error is:

2024-10-08 15:46:50.189 INFO MQTT: Message received on zwave/Garderobe/38/0/targetValue/set: '22'
2024-10-08 15:46:50.200 INFO MQTT: Message received on zwave/Garderobe/51/0/targetColor/set: '{"state":"ON","value":22}'
2024-10-08 15:46:50.191 INFO Z-WAVE: Writing 22 to 8-38-0-targetValue
2024-10-08 15:46:50.202 INFO Z-WAVE: Writing 22 to 8-51-0-targetColor
2024-10-08 15:46:50.209 ERROR Z-WAVE: Unable to write 22 on 51-0-targetColor: Color Switch: "targetColor" must be set to an object which specifies each color channel (ZW0322)

I don't understand why domoticz is sending 22 to targetColor while in the discovery payload it's very clear that:

        "rgb_command_template": "{{ {'red': red, 'green': green, 'blue': blue}|to_json }}",
		        "rgb_command_topic": "zwave/Garderobe/51/0/targetColor/set",

I would forward this request to domoticz team

[Thaui57]

Thanks for your survey. I believe that I have updated Domoticz to the last stable version 2024.7 before I updated Zwave js ui to 9.18.1. In 9.18.1 the dzvents script worked well and has changed the color as expected. Since 9.21.1 the malfunction appears. The dzvents script send the following command e.g: dz.devices(14).setColor(255,0,200,100,0,w,4,0). So I am not using the Domoticz GUI. I am sending via a test script color data but r,g,b 50,50,50 will be 2,0,2 in Zwave js ui

[robertsLando]

The dzvents script send the following command e.g: dz.devices(14).setColor(255,0,200,100,0,w,4,0). So I am not using the Domoticz GUI. I am sending via a test script color data but r,g,b 50,50,50 will be 2,0,2 in Zwave js ui

I dunno what you mean with dzevents script as I'm not a Domoticz user but as said the issue here is that the discovery rgb command template is not respected. It should send a JSON payload like:

{"red": 50, "green": 50, "blue": 50}

While it sends

{"state":"ON","value":22}

instead

[Thaui57]

the issue can be closed. after my door sensors also stoped working I flashed back a full SD card backup from Oktobera 1st. I am now back on zui 9.18.1 and zwavejs 13.2.0. System is back and operating well. Thanks for your support

[robertsLando]

yeah but you will need to upgrade one day or another and so I still don't understand what made it break in latest version

[EwoutSnel]

Experiencing the same issue with same Qubino RGBW dimmer. Made a forum post at Domoticz website.
https://www.domoticz.com/forum/viewtopic.php?t=42783
If possible please re-open.

[EwoutSnel]

@robertsLando if you have time, would you be so kind to read the post in the Domoticz forum? For me it is still unclear if this is a Domoticz bug or a Zwave-JS-UI bug.

[robertsLando]

@EwoutSnel Seems like domoticz is sending a wrong payload to targetColor, that payload makes no sense. If you revert to a previous working version what do you receive there? Did you checked if there are changes between the 2 discovery payloads sent by zui in the working and not working version? Comparing the 2 discovery payloads is the first thing to check

[Thaui57]

@robertsLando If there are no changes on the Domoticz platform and the rgbw dimmer works with zwave js UI version 9.18.1 but not with a newer version the problem is caused by zwavejs. Or am I wrong?

[robertsLando]

@Thaui57 I agree this is why I also asked to place here both discovery payload sent to domoticz (the working and not working one) as that is the only thing that could have break this. The command domoticz sent makes just no sense:

2024-10-08 15:46:50.200 INFO MQTT: Message received on zwave/Garderobe/51/0/targetColor/set: '{"state":"ON","value":22}'

[Thaui57]

@robertsLando not so easy in a productive system. I do my best do deliver a comparison log file soon. Otherwise we have no chance to sort it out. Thanks for your help

[Thaui57]

@robertsLando attached you will find two log files. One generated with 9.18.1 and the other 9.27.5. In the newer release the color change doesn't work. I hope that are the data you requested.
z-ui_2024-11-22_rel_9-18-1.log
z-ui_2024-11-22_rel_9-27-5.log