At the moment, I build up a new installation with some RGBW-Stripes, controlled by Fibaros RGBW-Controllers.
I read a lot of different items, I need for configuration.
Is it correct, that I need a Dimmer and a Colorpicker?
OH1 or 2 ?
OH2 zwave binding knows the COLOR command, you could get away with just this.
OH1 requires you to send single commands per R/G/B, so you need three more dimmers and a rule to convert the colorpicker output.
this are my settings. The rgbw-controller is working fine, except the colorpicker.
Maybe, like Markus suggested, I should create a rule to convert the colorpicker output. But at the moment I donāt know how.
Yes - it is working fine for me. I am however using the new development binding, but I donāt think thereās been changes to the color class from the master OH2 branch.
Sorry - I donāt really have any. I just included the device, clicked on the link item button and started using it. I did make a sitemap but it just says Colorpicker item=āā.
One other point is Iām possibly using a reasonably new version of the RGBW so maybe thereās problems with older versions. Alternatively, it might be worth trying the new binding, but thatās not for the faint hearted as itās a bit of a change.
So we can conclude for now that my old device is not usable with the new color class then and therefore not usable in paperui.
i am realy curious to see how the new versions of the binding will support this, the RGBW controller has always been an issue to get working correctly , i assumed that the color class would solve that as it is the item replacing all the rules.
I think we must be patient untill chris has finished the new binding so we can test it.
thank you for clarifying this chris , then i can stop my search for now untill the new one is out.
if you need an xml or any info on older devices , count me in i have allot of them .
As I think I said previously (maybe the other thread) the new binding has the same color command class as the current OH2 binding, so donāt expect it to change. Maybe the new code works better in general with this device (maybe!) but I donāt think the command class is different.
Iām not sure what you mean by this? The binding, and command classes etc arenāt linked to rules in any way.
Iāll take a look at the log if you want to send one (debug of course ). Best is to raise a ticket on my website so I donāt loose it, and you can attach log files there easily.
sorry, I just realized that I didnāt answer your last question.
Because I have one favorite colour-setting, I donāt change colours and thatās why I donāt convert or send values.
I only use this simple rule to turn on the led-strips:
rule "Szene_01_Sofa-Licht_An"
when //
Item N05AeotecMultiSensor6Wohnen_BinarySensor changed from OFF to ON //wenn im Wohnzimmer Bewegung erkannt wird, dann prĆ¼fe ...
then
logInfo("Demo","Wohnen_LichtAutomatik.rules Szene_01_Sofa-Licht_An: N05Bewegung getriggert. N03ErlaubeAutoEin="+N03FibaroRGBWControllerWohnen_ErlaubeAutoEin.state.toString+" N03LichtIstAn="+N03FibaroRGBWControllerWohnen_Dimmer.state.toString+" N05Helligkeit="+N05AeotecMultiSensor6Wohnen_SensorLuminance.state.toString)
if (N03FibaroRGBWControllerWohnen_ErlaubeAutoEin.state == ON //wenn EinschaltAutomatik an
&& N03FibaroRGBWControllerWohnen_Dimmer.state != ON //und wenn Licht nicht bereits an (sonst wĆ¼rden aktuelle Einstellungen verƤndert)
&& N05AeotecMultiSensor6Wohnen_SensorLuminance.state < 4 //und wenn Helligkeit unter Grenzwert
) {
sendCommand(N03FibaroRGBWControllerWohnen_Dimmer, ON) //dann Sofa-Licht mit den zuletzt verwendeten Einstellungen einschalten
}
end
Hi, Iām resuming this old thread since I just bought a fibaro RGBW module and Iām facing some issues with the HSB color channel.
In details:
When I change che strip color from the Colorpicker the brightness value is reduced to a lower level. So any time I change the color I need to re-increase the brightness value.
it seems that the color channel has no control on the white channel. Is this the expected behavior or the color channel should control all the 4 RGBW channels?
Please let me know if I should change some option in opnehab2 configuration on the advanced fibaro RGBW parameters. Especially to resolve issue 1 that is very annoying.
Please use debug level output of zwave to see if itās the same values being sent to the device to result in different brightnesses (might be a bug in binding or device, then).
Yes thatās to be expected. The W channel needs to be separately controlled by a dimmer item.
Hi Markus, thank you for the hint.
I have been able to generate the zwave debug log but not sure about what I have to look for.
The log of a single command is around 500 lines, could I share it with you, or could you point me the section I have to investigate?
Thank you
after some time looking to the log it seem to me that the stateChangeEvent is properly performed:
[vent.ItemStateChangedEvent] - Luce_Striscia_Colore changed from 0,93,100 to 231,97,100
but even if the value initially is 100 and is changed to 100 the strip reduce its brightness.
if I run as second command whit a brightness change:
[ome.event.ItemCommandEvent] - Item āLuce_Strisciaā received command 100
the strip generates additional light keeping the color.