Malfunctioning Qubino Flush RGB dimmer ZMNHWD3 device on openhab

fifo · February 21, 2018, 12:29pm

Hello everyone, having an issue with a Qubino Flush RGB dimmer ZMNHWD3. I have been able to install it and am able to control the white lights alone but the RGB lights do not react to anything I do. I am fairly new to openHAB so I am not sure where to look.

I have tried removing and adding the device again. I am running on the latest openHAB snapshot release openHAB 2.3.0 Build #1219. It seems to me like the definition of the z-wave device is incorrect. I have checked in the http://www.cd-jackson.com/ site and the device is in the list but there is a mention that says its for ZMNHWD1 but that it should hopefully work with the others. I believe the 1 just indicates a country code of some sort. ( basically the frequency the device operates in ).

Would be able to point me in he right direction? I’m not sure what to check. I haven’t been able to find where the definition of the device is in my setup. I am running it on a vanilla Ubuntu desktop if that helps any.

rlkoshak · February 21, 2018, 7:27pm

Please post your relevant Items. Are you using an Item linked to the color channel to send the color commands to?

fifo · February 22, 2018, 12:29am

I added the device using PaperUI and these are my things and the items linked to them. Looks like the Color Contol item is what you are asking for. Let me know if there is anything else I can add here to help.

rlkoshak · February 22, 2018, 12:35am

What I’m asking is to make sure you are sending color commands to the item linked to color channel.

fifo · February 22, 2018, 1:11am

Bringing it up on the control window, when I select a color it doesn’t do anything. The color temperature seems to dim just a tad bit but that is all.

fifo · February 22, 2018, 1:15am

I imagine this is what you want to see…

==> events.log <==
2018-02-21 20:14:41.972 [ome.event.ItemCommandEvent] - Item 'Node7_ColorControl' received command 134,0,0
2018-02-21 20:14:41.974 [vent.ItemStateChangedEvent] - Node7_ColorControl changed from 94,0,0 to 134,0,0

fifo · February 26, 2018, 12:26pm

Still haven’t been able to find anything. I noticed that the color temperature seems to have a mind of its own. If I set it to something other than 0, at times it will move itself back to 0. Not sure how that is happening.

Anything else I should try? The log looks normal to me.

Kjamsek · March 6, 2018, 2:06pm

This looks like an incomplete implementation of the Color Switch Command Class, as defined by the Z-Wave protocol.

If you look at the log you’ve pasted you can only see three values being set. I assume these are the RGB channels, respectively.

Z-Wave defines a number of available channels in the Color Switch CC, Warm White, Cold White, Red, Green, Blue, …

The saturation slider (and hue options and potentially the brightness setting) doesn’t have a direct influence on Z-Wave communication, since the device’s supported command classes do not implement hue and saturation scales, but instead use RGBW channel colors.

In the example you’ve shown the log only shows 3 values, wheres the device in question supports 4 color channels (RGB and warm white if i recall correctly). Additionally, as per the Z-Wave protocol specs, the dimming percentage is a separate scale from the color values, so it’s entirely possible that the GW instructs the device to cut it’s dimming value, which could cause the device to turn off.

Another option to look at is if you’ve deactivated it via the device’s input buttons.

fifo · March 7, 2018, 1:45am

Thinking along the same lines, I have reset the device to factory. I thought it might have been something I did that caused it to malfunction but that did nothing. I then paired the device at a friends home with the smartthings hub and it worked with no issues. Brought back home and paired with openhab and back to the same problem.

I imagine if its the implementation of the switch, I should be able to hack at it locally. I’m just not quite sure where to start. I visited cd-jackson.com and see this “http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/567” . The Color control and color temperature seem to be included in there.

Here is some more of my log. Could that be HSB values instead of RGB? See below, the numbers go above 255 towards the very end.

=> openhab.log <==
2018-03-06 20:39:15.311 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report RED 0
2018-03-06 20:39:15.312 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=194}
2018-03-06 20:39:15.554 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report GREEN 0
2018-03-06 20:39:15.554 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=194}
2018-03-06 20:39:15.758 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report BLUE 0
2018-03-06 20:39:15.758 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=194}
2018-03-06 20:39:15.956 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report WARM_WHITE 255
2018-03-06 20:39:15.956 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=255}

==> events.log <==
2018-03-06 20:39:17.760 [ome.event.ItemCommandEvent] - Item 'zwave_device_7b2f526d_node9_color_color' received command 199,0,0
2018-03-06 20:39:17.762 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 0,0,0 to 199,0,0
2018-03-06 20:39:20.855 [ome.event.ItemCommandEvent] - Item 'zwave_device_7b2f526d_node9_color_color' received command 199,72,0
2018-03-06 20:39:20.857 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 199,0,0 to 199,72,0
2018-03-06 20:39:23.444 [ome.event.ItemCommandEvent] - Item 'zwave_device_7b2f526d_node9_color_color' received command 80
2018-03-06 20:39:23.446 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 199,72,0 to 199,72,80

==> openhab.log <==
2018-03-06 20:39:23.762 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report RED 0
2018-03-06 20:39:23.762 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=255}

==> events.log <==
2018-03-06 20:39:23.766 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 199,72,80 to 0,0,0

==> openhab.log <==
2018-03-06 20:39:24.003 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report GREEN 0
2018-03-06 20:39:24.004 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=255}
2018-03-06 20:39:24.203 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report BLUE 0
2018-03-06 20:39:24.204 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=255}

==> events.log <==
2018-03-06 20:39:24.352 [ome.event.ItemCommandEvent] - Item 'zwave_device_7b2f526d_node9_color_color' received command 100
2018-03-06 20:39:24.355 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 0,0,0 to 0,0,100

==> openhab.log <==
2018-03-06 20:39:24.508 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report WARM_WHITE 207
2018-03-06 20:39:24.509 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=207}

==> events.log <==
2018-03-06 20:39:24.511 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 0,0,100 to 0,0,0

==> openhab.log <==
2018-03-06 20:39:26.936 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report WARM_WHITE 207
2018-03-06 20:39:26.936 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=207}

==> events.log <==
2018-03-06 20:39:27.328 [ome.event.ItemCommandEvent] - Item 'zwave_device_7b2f526d_node9_color_color' received command 305,0,0
2018-03-06 20:39:27.330 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 0,0,0 to 305,0,0
2018-03-06 20:39:27.642 [ome.event.ItemCommandEvent] - Item 'zwave_device_7b2f526d_node9_color_color' received command 360,0,0
2018-03-06 20:39:27.644 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 305,0,0 to 360,0,0

Kjamsek · March 7, 2018, 7:52am

Seeing as you’ve tried it on SmartThings, and encountered no issues there, the device itself must be functioning correctly.

If you have the option to, you can also test it via the handler i made for SmartThings for the RGBW Dimmer, available here (SmartThings uses HSB so i’ve had to do conversions in order to support RGBW channels as per the Z-Wave protocol):

I’d say the issue is probably in HSB conversion, as you’ve noted, since the values you’ve received are greater htan 255 (which cannot be the case with RGBW since 255 is the largest decimal value allowed for a single channel).

An additional arguement that would point at this is the fact that even when you get values from the device the ones reported don’t seem to match the ones in the event log (if these are tied to the RGB values or HSB i really can’t be sure without knowing the code).
I sincerely doubt you’d be able to interact with the device physically inside 280ms that ocurred between these events, which could potentially change the values on the device:

2018-03-06 20:39:23.446 [vent.ItemStateChangedEvent] - zwave_device_7b2f526d_node9_color_color changed from 199,72,0 to 199,72,80
==> openhab.log <==
2018-03-06 20:39:23.762 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report RED 0
2018-03-06 20:39:23.762 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 9: Color report finished {GREEN=0, BLUE=0, RED=0, WARM_WHITE=255}

fifo · March 10, 2018, 2:38am

Unfortunately I don’t have access to the smart thing hub any longer so I wont be able to try it. Not really sure where I can go from here but I will keep googling my way through this till I find a solution.

goopilot · April 24, 2018, 5:16am

Were you able to resolve your problem? I have identical issue. I can only change brightness, not the color.

fifo · April 24, 2018, 10:49am

Unfortunately I haven’t been able to find any way to fix it yet.

goopilot · April 25, 2018, 3:43am

maybe @chris can advise. From what I see according to manual there are definitely missed configuration parameters.

chris · April 25, 2018, 7:16am

I’m not sure what the problem is - I’d need to see a log.

I’ll answer to a few comments though from above as I’ve not seen this before -:

Yes - the binding only uses a reduced set of colours - when setting RGB, it only sets the RGB. When setting whites, it uses the white channels. The other colours aren’t normally used, but I don’t see what this is a problem and doesn’t make it incomplete.

I don’t see any RGB numbers above 255, so I’m not sure what you’re looking at. The RGB conversion is unlikely to be the problem as it is using the code from ESH - ie the same for every other binding. If you have an example of high numbers being returned, then please provide it as the log I see here does not show RGB values above 255 that I can see.

Again - I must be missing something as I don’t see RGB values above 255. Please can someone provide this?

I can take a look at this, but only if someone can provide a debug log file to look at.

chris · April 26, 2018, 7:09am

Looking at the log, I think the issue is simply that the database is not configured properly. It is not sending the color commands at all due to this.

I’ll update the database and hopefully that will solve the issue.

goopilot · April 28, 2018, 3:53am

There are also many configuration parameters missing according to attached manual. I can add them.

fifo · April 28, 2018, 9:10am

Let me know when you would like me to test and if there is anything I can do to help. Not too familiar with all of this yet but I can get around a little.

chris · April 28, 2018, 9:40am

Thanks @goopilot - I’ve approved this and will hopefully do a binding update later today/tonight.

fifo · April 29, 2018, 8:51pm

@chris Did you get to make the changes to yesterdays build? If so, it’s still not working after updating to that build. Would I need to remove and add device again for changes to take?