Closed jeroenst closed 6 years ago
try to changes the Color Channels with 31.
Actual the bulb turns blue but the value received from openzwave says it is 0..
I don't understand what you mean witj change the color channels with 31..
I also see in the log that open-zwave is only requesting color register 0 - 3.
According to the zwave specification it'snot requesting the blue color:
0 Warm White 0x00 – 0xFF: 0 – 100% 1 Cold White 0x00: - 0xFF: 0 – 100% 2 Red 0x00 – 0xFF: 0 – 100% 3 Green 0x00 – 0xFF: 0 – 100% 4 Blue 0x00 – 0xFF: 0 – 100% 5 Amber (for 6ch Color mixing) 0x00 – 0xFF: 0 – 100% 6 Cyan (for 6ch Color mixing) 0x00 – 0xFF: 0 – 100% 7 Purple (for 6ch Color mixing) 0x00 – 0xFF: 0 – 100% 8 Indexed Color 0x00 – 0xFF: Color Index 0-255
Color Channels is a System value. I don't know how to change value with our gateway. in jeedom is strike-forward. I also have this bulb with same behavior, if I set the Color Channels to 31, I receive right color report
You're right, setting colorchannels to 31 works, thanks...
The Zipato bulb return 15 (channels 1,2,3 and 4) when nr of channels is requested which should be 31 (channels 1,2,3,4 and 5).
So maybe it's possible to create a workaround for Zipato Bulb 2 in the zwave library?
Okay, I made a workaround in the zwave library, will create a pull request in a few minutes..
I've created a pull request fixing this issue..
Could you provide a log showing the get capabilities query (and response?)
Or could you confirm if its a off by 1 issue (eg, index based on 1 rather than 0 in the spec). Its unusual to see a "warm white" and "cold white" in the same bulb (at least I've not seen it yet)
Yes this bulb has warm white and cold white leds in the same bulb. Please wait for logging, i will provide it later.
Logging as requested (as you can see no Blue color is reported and warm and cold white is):
2018-03-07 08:25:52.342 Info, Node011, Sending (Query) message (Callback ID=0x42, Expected Reply=0x04) - ColorCmd_CapabilityGet (Node=11): 0x01, 0x09, 0x00, 0x13, 0x0b, 0x02, 0x33, 0x01, 0x25, 0x42, 0xb9 2018-03-07 08:25:52.349 Detail, Node011, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2018-03-07 08:25:52.349 Detail, Node011, ZW_SEND_DATA delivered to Z-Wave stack 2018-03-07 08:25:52.365 Detail, Node011, Received: 0x01, 0x07, 0x00, 0x13, 0x42, 0x00, 0x00, 0x02, 0xab 2018-03-07 08:25:52.365 Detail, Node011, ZW_SEND_DATA Request with callback ID 0x42 received (expected 0x42) 2018-03-07 08:25:52.365 Info, Node011, Request RTT 23 Average Request RTT 23 2018-03-07 08:25:52.376 Detail, Node011, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x0b, 0x04, 0x33, 0x02, 0x0f, 0x00, 0xc0 2018-03-07 08:25:52.377 Info, Node011, Response RTT 34 Average Response RTT 34 2018-03-07 08:25:52.377 Info, Node011, Received an Color Capability Report: Capability=fd 2018-03-07 08:25:52.377 Info, Node011, Red (0x02) 2018-03-07 08:25:52.377 Info, Node011, Green (0x03) 2018-03-07 08:25:52.377 Info, Node011, Warm White (0x00) 2018-03-07 08:25:52.377 Info, Node011, Cold White (0x01)
Here is logging with my patch:
2018-03-07 08:52:33.265 Info, Node011, Sending (Query) message (Callback ID=0x40, Expected Reply=0x04) - ColorCmd_CapabilityGet (Node=11): 0x01, 0x09, 0x00, 0x13, 0x0b, 0x02, 0x33, 0x01, 0x25, 0x40, 0xbb 2018-03-07 08:52:33.273 Detail, Node011, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2018-03-07 08:52:33.273 Detail, Node011, ZW_SEND_DATA delivered to Z-Wave stack 2018-03-07 08:52:33.289 Detail, Node011, Received: 0x01, 0x07, 0x00, 0x13, 0x40, 0x00, 0x00, 0x02, 0xa9 2018-03-07 08:52:33.289 Detail, Node011, ZW_SEND_DATA Request with callback ID 0x40 received (expected 0x40) 2018-03-07 08:52:33.289 Info, Node011, Request RTT 24 Average Request RTT 24 2018-03-07 08:52:33.300 Detail, Node011, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x0b, 0x04, 0x33, 0x02, 0x0f, 0x00, 0xc0 2018-03-07 08:52:33.300 Info, Node011, Response RTT 35 Average Response RTT 35 2018-03-07 08:52:33.301 Info, Node011, Received an Color Capability Report: Capability=1fd 2018-03-07 08:52:33.301 Info, Node011, Red (0x02) 2018-03-07 08:52:33.301 Info, Node011, Green (0x03) 2018-03-07 08:52:33.301 Info, Node011, Blue (0x04) 2018-03-07 08:52:33.301 Info, Node011, Warm White (0x00) 2018-03-07 08:52:33.301 Info, Node011, Cold White (0x01)
Okay, pull request is ready... https://github.com/OpenZWave/open-zwave/pull/1459
Ok - Buggy device. Please report to Zipato so they can fix in a future version.
In the mean time, no need to create a PR, the capabilities can already be specified in the config file with a
colorchannels="31"
in the zapato config file and removing the ozw_config.xml file
Typo it should be colorchannels="31"
Do you have an example so I can update the open-zwave/config/RGBBulb2.xml and create a pull request?
Or even better, can you fix this in the next commit to open-zwave repo?
Sorry, I see your label ConfigUpdate, I suppose you're taking care of it..
Thanx in advance!
Nope - I don't have a device to test. See https://github.com/OpenZWave/open-zwave/blob/725277e2ce1ba1bf7899e11a814f6447f03a2ea2/config/fibaro/fgrgbwm441.xml#L13 but instead of coloridxbug, use colorchannels
I made a new pull request which I have tested and informed zipato about this bug.
When I set the blue color value of the Zipato Bulb 2, the blue value returned from open-zwave is always 00