RGBW Qubino dimmer - setcolor not working

[Ewout]

Using Domoticz Stable 2024.7 in Docker on Debian.

With newest version of Z-Wave JS UI (and MQTT) I'm experiencing the same issue as described here: https://github.com/zwave-js/zwave-js-ui/issues/3924

When I adjust the color directly in Z-Wave JS UI, I see the device functioning perfectly. The change is also neatly transferred to Domoticz via MQTT.

When I try to adjust the color in Domoticz, nothing happens. Only level changes seems to reach Z-Wave JS UI. The color changes are not 'understood'.

Log Z-Wave JS UI:
2024-10-26 19:57:43.671 INFO STORE: Message received on zwave/24V_LED_driver/51/0/targetColor/set: '{"state":"ON"}'
2024-10-26 19:57:43.671 INFO STORE: Writing { state: 'ON' } to 17-51-0-targetColor
2024-10-26 19:57:43.671 ERROR STORE: Unable to write { state: 'ON' } on 51-0-targetColor: Color Switch: "targetColor" must be set to an object which specifies each color channel (ZW0322)

Also through the API, the color is not changing for me when I make a request with a HEX code.
<<my ip>>:<<my port>>/json.htm?type=command&param=setcolbrightnessvalue&idx=477&hex=FF0000&brightness=100&iswhite=false
This has always worked for me!

I have also reverted zwave-js-ui to version 9.18 and immediately afterwards I could change the color in Domoticz as usual.

I am not a programmer, but I would like to help solve this issue. Please let me know what you need.

[elgringo]

I got the same issue.

I got a feeling the interface has been changed

[jberinga]

My Domoticz is also unable to change the color but on a Zipato E27 led bulb...

[waltervl]

Using Domoticz Stable 2024.7 in Docker on Debian.

With newest version of Z-Wave JS UI (and MQTT) I'm experiencing the same issue as described here: https://github.com/zwave-js/zwave-js-ui/issues/3924

When I adjust the color directly in Z-Wave JS UI, I see the device functioning perfectly. The change is also neatly transferred to Domoticz via MQTT.

When I try to adjust the color in Domoticz, nothing happens. Only level changes seems to reach Z-Wave JS UI. The color changes are not 'understood'.

Log Z-Wave JS UI:
2024-10-26 19:57:43.671 INFO STORE: Message received on zwave/24V_LED_driver/51/0/targetColor/set: '{"state":"ON"}'
2024-10-26 19:57:43.671 INFO STORE: Writing { state: 'ON' } to 17-51-0-targetColor
2024-10-26 19:57:43.671 ERROR STORE: Unable to write { state: 'ON' } on 51-0-targetColor: Color Switch: "targetColor" must be set to an object which specifies each color channel (ZW0322)

Also through the API, the color is not changing for me when I make a request with a HEX code.
<<my ip>>:<<my port>>/json.htm?type=command&param=setcolbrightnessvalue&idx=477&hex=FF0000&brightness=100&iswhite=false
This has always worked for me!

I have also reverted zwave-js-ui to version 9.18 and immediately afterwards I could change the color in Domoticz as usual.

I am not a programmer, but I would like to help solve this issue. Please let me know what you need.

It seems that if from Zwave-JS-UI the color setting goes correctly the first place to look is into Domoticz.
To report issues with MQTT AutoDiscover that Zwave-JS-UI is using to communicate with Domoticz use the instructions on the wiki:
https://www.domoticz.com/wiki/MQTT_AD_Report_Problems

You could also compare the MQTT messages when changing color in Zwave-JS-UI with the MQTT message when changing color in Domoticz.

[thaui]

I have the same issue with the newest ZWAVE js ui and I am gone back to 9.18.1 which worked for me again. It seems to be a zwave is ui problem. I have reported thtat month ago to Zwave Js ui as a bug.

[Ewout]

Below some details I found in the MQTT explorer. For me this is all new, so bare with me. Right now all is working fine with Zwave-JS-UI version 9.18

Below the config payload of the RGB dimmer:

Code: Select all

{
  "state_topic": "zwave/24V_LED_driver/38/0/currentValue",
  "command_topic": "zwave/24V_LED_driver/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 }}",
  "rgb_state_topic": "zwave/24V_LED_driver/51/0/currentColor",
  "rgb_command_topic": "zwave/24V_LED_driver/51/0/targetColor/set",
  "brightness_state_topic": "zwave/24V_LED_driver/38/0/currentValue",
  "brightness_command_topic": "zwave/24V_LED_driver/38/0/targetValue/set",
  "availability": [
    {
      "payload_available": "true",
      "payload_not_available": "false",
      "topic": "zwave/24V_LED_driver/status",
      "value_template": "{{'true' if value_json.value else 'false'}}"
    },
    {
      "topic": "zwave/_CLIENTS/ZWAVE_GATEWAY-zwave-js-ui/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_0xe2118c93_node17"
    ],
    "manufacturer": "Qubino",
    "model": "Qubino Flush RGBW Dimmer (ZMNHWD)",
    "name": "24V LED driver",
    "sw_version": "2.7"
  },
  "name": "24V LED driver_rgb_dimmer",
  "unique_id": "zwavejs2mqtt_0xe2118c93_17-51-0-currentColor"
}

Below the last succesfully rgb_state change:

Code: Select all

{
  "time": 1731361672168,
  "value": {
    "warmWhite": 0,
    "red": 0,
    "green": 255,
    "blue": 0
  },
  "nodeName": "24V LED driver",
  "nodeLocation": "Berging"
}

After upgrade to the latest Zwave-JS-UI version - NOT WORKING SITUATION:

MQTT message when I sucessfully change the color in the node in Zwave-JS-UI:

Code: Select all

{
  "time": 1731363004256,
  "value": {
    "warmWhite": 0,
    "red": 0,
    "green": 0,
    "blue": 255
  },
  "nodeName": "24V LED driver",
  "nodeLocation": "Berging"
}

When I try to push red color (LED strip in my bathroom) through Domoticz, this is the log in Domoticz:

Code: Select all

2024-11-11 23:23:11.467 Z-Wave: Light/Switch/Switch (PIR badkamer)
2024-11-11 23:23:11.484 EventSystem: Event triggered: 24V LED verlichting_10
2024-11-11 23:23:11.484 Status: EventSystem: Fetching URL 127.0.0.1:8085/json.htm?type=command&param=setcolbrightnessvalue&idx=477&hex=ff0000&brightness=100&iswhite=false after 0.2 seconds...
2024-11-11 23:23:11.484 Status: Berging UIT - Badkamer AAN - Hal UIT
2024-11-11 23:23:11.712 Status: setcolbrightnessvalue: ID: 1dd, bri: 100, color: '{m: 3, RGB: ff0000, CWWW: 0000, CT: 0}'
2024-11-11 23:23:11.920 Z-Wave: Color Switch/RGBWZ (24V LED color)

But there is no new MQTT message. I think the message doesn't get understood somehow. I think I do see a new MQTT message, but it looks like a repeat of the previous state in MQTT. So this is not with the correct color.

This is the log in Zwave-JS-UI:

Code: Select all

2024-11-11 23:23:11.714 INFO STORE: Message received on zwave/24V_LED_driver/38/0/targetValue/set: '99'
2024-11-11 23:23:11.715 INFO STORE: Writing 99 to 17-38-0-targetValue
2024-11-11 23:23:11.718 INFO STORE: Message received on zwave/24V_LED_driver/51/0/targetColor/set: '{"state":"ON","value":99}'
2024-11-11 23:23:11.718 INFO STORE: Writing 99 to 17-51-0-targetColor
2024-11-11 23:23:11.719 ERROR STORE: Unable to write 99 on 51-0-targetColor: Color Switch: "targetColor" must be set to an object which specifies each color channel (ZW0322)

It looks like Domoticz tries to write the level of the dimmer twice, but not the color! Or it's get misunderstood by Zwave-JS-UI.
17-38-0 specifies the level of the dimmer
17-51-0 specifies the color

So far my knowledge. What should be my next move?

[thaui]

@Ewout Have you found a solution which works?

[Ewout]

Does anybody know if Domoticz support supported_color_modes correctly in MQTT autodiscovery?