-
-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RGBW dimmer is not reacting on color changes #3924
Comments
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? |
how can I downgrade to 9.18.1 |
@Thaui57 Just specify |
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 |
Seems the error is:
I don't understand why domoticz is sending 22 to targetColor while in the discovery payload it's very clear that:
I would forward this request to domoticz team |
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 |
I dunno what you mean with {"red": 50, "green": 50, "blue": 50} While it sends {"state":"ON","value":22} instead |
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 |
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 |
Experiencing the same issue with same Qubino RGBW dimmer. Made a forum post at Domoticz website. |
@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. |
@EwoutSnel Seems like domoticz is sending a wrong payload to |
@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? |
@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:
|
@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 |
@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. |
@Thaui57 thanks for the logs 🙏🏼 Discovery from 9.18.1: {
type: 'light',
object_id: 'rgb_dimmer_1',
discovery_payload: {
state_topic: 'zwave/Arbeitszimmer_LED/38/1/currentValue',
command_topic: 'zwave/Arbeitszimmer_LED/38/1/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/Arbeitszimmer_LED/51/1/currentColor',
rgb_command_topic: 'zwave/Arbeitszimmer_LED/51/1/targetColor/set',
brightness_state_topic: 'zwave/Arbeitszimmer_LED/38/1/currentValue',
brightness_command_topic: 'zwave/Arbeitszimmer_LED/38/1/targetValue/set',
availability: [
{
payload_available: 'true',
payload_not_available: 'false',
topic: 'zwave/Arbeitszimmer_LED/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'
},
[length]: 3
],
availability_mode: 'all',
device: {
identifiers: [ 'zwavejs2mqtt_0xdbf01f81_node47', [length]: 1 ],
manufacturer: 'Fibargroup',
model: 'RGBW CONTROLLER 2 (FGRGBW-442)',
name: 'Arbeitszimmer LED',
sw_version: '5.0'
},
name: 'Arbeitszimmer LED_rgb_dimmer_1',
unique_id: 'zwavejs2mqtt_0xdbf01f81_47-51-1-currentColor'
},
values: [
'38-1-currentValue',
'38-1-targetValue',
'51-1-currentColor',
'51-1-targetColor',
[length]: 4
],
discoveryTopic: 'light/Arbeitszimmer_LED/rgb_dimmer_1/config',
persistent: false,
ignoreDiscovery: false
} Discovery from 9.27.5 {
type: 'light',
object_id: 'rgb_dimmer_1',
discovery_payload: {
state_topic: 'zwave/Arbeitszimmer_LED/38/1/currentValue',
command_topic: 'zwave/Arbeitszimmer_LED/38/1/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', [length]: 2 ],
rgb_state_topic: 'zwave/Arbeitszimmer_LED/51/1/currentColor',
rgb_command_topic: 'zwave/Arbeitszimmer_LED/51/1/targetColor/set',
brightness_state_topic: 'zwave/Arbeitszimmer_LED/38/1/currentValue',
brightness_command_topic: 'zwave/Arbeitszimmer_LED/38/1/targetValue/set',
availability: [
{
payload_available: 'true',
payload_not_available: 'false',
topic: 'zwave/Arbeitszimmer_LED/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'
},
[length]: 3
],
availability_mode: 'all',
device: {
identifiers: [ 'zwavejs2mqtt_0xdbf01f81_node47', [length]: 1 ],
manufacturer: 'Fibargroup',
model: 'RGBW CONTROLLER 2 (FGRGBW-442)',
name: 'Arbeitszimmer LED',
sw_version: '5.0'
},
name: 'Arbeitszimmer LED_rgb_dimmer_1',
unique_id: 'zwavejs2mqtt_0xdbf01f81_47-51-1-currentColor'
},
values: [
'38-1-currentValue',
'38-1-targetValue',
'51-1-currentColor',
'51-1-targetColor',
[length]: 4
],
discoveryTopic: 'light/Arbeitszimmer_LED/rgb_dimmer_1/config',
persistent: false,
ignoreDiscovery: false
} The only thing changed between this two discovery payload is Question is if domoticz handles this correctly or not, I have a feel that if you remove that from discovery it will work as expected. This change has been added in order to fix #3894 and first release with that has been 9.19.0 |
So this are the steps I did:
RGB dimmer is now working as before and as expected! However this change does NOT survive a restart of Zwave-JS-UI....... Any ideas how to make this change persistent? |
I would have no clue how strictly Domoticz adheres to the HA MQTT discovery schema, but this payload value is invalid. See docs: https://www.home-assistant.io/integrations/light.mqtt/#supported_color_modes
|
Oh maybe the issue is that so, but if the device supports both brightness and RGB should I only report rgb so? Or maybe rgbw? |
@robertsLando is there any improvement on this issue? |
@Thaui57 Could you try to manually edit the json and changing the |
Changed this: Into this: Afterwards I did a reboot of Domoticz container. Unfortunately the color changes do NOT work with this change, as far as I can tell. @Thaui57 can you also test this? |
Should it be this?
There was no indication of RGBW support in the original discovery schema (except the product name), and the brightness flag is there to indicate brightness + rgb/rgbw/rgbww. |
@Thaui57 @EwoutSnel could you try kpine suggestion? Also I would put the values between square brackets as that is a list:
|
Thanks, that's right. (fixed my original) |
Sorry guys, still no success with this suggestion. The only working solution is to completely remove the "supported_color_modes" line from the json. |
Perhaps you should setup a test instance of HA with MQTT and see if it works there. If working in HA, then it's a Domoticz problem. |
@EwoutSnel could you try asking to Domotiz team if they support |
Checklist
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
The text was updated successfully, but these errors were encountered: