OpenHAB 3 Z-Wave FGRGBW-442 RGBW Controller Fibaro LED light strip won't turn on

[SethEden (Seth Hollingsead)]

• Platform information:

  • Hardware: Intel i5/x86/16gb/4TB HD / 1TB SSD

  • OS: Windows10

  • Java Runtime Environment: openjdk version “11.0.11” 2021-04-20 LTS
    OpenJDK Runtime Environment Zulu11.48+21-CA (build 11.0.11+9-LTS)
    OpenJDK 64-Bit Server VM Zulu11.48+21-CA (build 11.0.11+9-LTS, mixed mode)

  • openHAB version: 3.0.2

• Issue of the topic: I’ve been wanting to implement an OpenHAB system for like 10 years and now finally it is happening!! I’ve decided to start with implementing a smart lighting system for my new custom smart gaming desk. I’ve ordered 13 Fibaro RGBW LED controllers and 13 RGBW LED light strips. I purchased a simple Z-Stick Gen5 and setup the basic system for the first time. I got the Z-stick controller installed and running as a Thing and then added the Fibaro to the Z-Wave network. The Fibaro controller Thing shows as online so I added a Color Control and TestLight and bridged them. However, when I set the color value on the color control or even when I try to go straight into the Fibaro thing and change it’s color values they are automatically reset back to 0,0,0 after about 1 second. There is a massive set of configuration settings which I have no idea about! I’m sure I’m going to have a ton of questions on all of this stuff as I try to learn it all. Is there a Discord channel to help with chatting and learning?

What I’m trying to accomplish right now: I just want to get one controller and one light up and running so I can learn enough to validate that all the components are working correctly before going into a full deep installation on the actual desk.

• Please post configurations (if applicable):
  This is the configuration settings that I see.
  1: Remember device status before the power failure = 0
  20: Input 1 - Operating mode = 2
  21: Input 2 - Operating mode = 2
  22: Input 3 - Operating mode = 2
  23: Input 4 - Operating mode = 2
  30: Alarm configuration - 1st slot = 0
  31: Alarm configuration - 2nd slot = 0
  32: Alarm configuration - 3rd slot = 0
  33: Alarm configuration - 4th slot = 0
  34: Alarm configuration - 5th slot = 0
  35: Duration of alarm signalization = not set
  40: Input 1 - sent scenes = 15
  41: Input 2 - sent scenes = 15
  42: Input 3 - sent scenes = 15
  43: Input 4 - sent scenes = 15
  62: Power reports - periodic = 3600
  63: Analog inputs output change on input change = 5
  64: Analog inputs reports - periodic = 0
  65: Energy reports - on change = 10
  66: Energy reports - periodic = 3600
  150: Inputs - LED colour control mode = 0 (I tried to change to to 1 & 2, but no luck)
  151: Local control - transition time = 3
  152: Remote control - transition time = 3
  154: ON frame value for single click IN1 = 255
  154: ON frame value for single click IN2 = 255
  154: ON frame value for single click IN3 = 255
  154: ON frame value for single click IN4 = 127
  155: OFF frame value for single click IN1 = 0
  155: OFF frame value for single click IN2 = 0
  155: OFF frame value for single click IN3 = 0
  155: OFF frame value for single click IN4 = 0
  156: ON frame value for double click IN1 = 99
  156: ON frame value for double click IN2 = 99
  156: ON frame value for double click IN3 = 99
  156: ON frame value for double click IN4 = 99
  157: Start programmed sequence = 0

Under Association Groups I tried to change some of the settings, but none of them persist, all changes are reset.

Device Configuration:
Polling Period: 86400
Command Poll Period: 1500

• Items configuration related to the issue
  Z-Wave Node 003: FGRGBW-442 RGBW CONTROLLER 2
  Group - Equipment>LightStripe = NULL (I am not able to change the NULL value no matter what I do!)

• If logs where generated please post these here using code fences:

17:51:10.181 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command 283,78,86
17:51:10.181 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become 283,78,86
17:51:10.182 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 283,84,87 to 283,78,86
17:51:10.185 [WARN ] [nternal.converter.ZWaveColorConverter] - NODE 3: Unknown color mode null.
17:51:10.381 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command 283,82,85
17:51:10.381 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become 283,82,85
17:51:10.382 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 283,78,86 to 283,82,85
17:51:10.384 [WARN ] [nternal.converter.ZWaveColorConverter] - NODE 3: Unknown color mode null.
17:51:10.838 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 283,82,85 to 0,0,0
17:51:11.955 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,0,0 to 0,0,100
17:51:11.955 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'TestLight' changed from 0,0,0 to 0,0,100
17:51:12.181 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,0,100 to 0,0,0
17:51:12.181 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'TestLight' changed from 0,0,100 to 0,0,0
18:07:49.388 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command ON
18:07:49.388 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become ON
18:07:49.389 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,0,0 to 0,0,100
18:07:50.953 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'TestLight' changed from 0,0,0 to 0,0,100
18:07:51.178 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,0,100 to 0,0,0
18:07:51.179 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'TestLight' changed from 0,0,100 to 0,0,0
18:07:55.986 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command 0,61,81
18:07:55.986 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become 0,61,81
18:07:55.987 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,0,0 to 0,61,81
18:07:55.991 [WARN ] [nternal.converter.ZWaveColorConverter] - NODE 3: Unknown color mode null.
18:07:56.193 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command 0,96,95
18:07:56.194 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become 0,96,95
18:07:56.195 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,61,81 to 0,96,95
18:07:56.197 [WARN ] [nternal.converter.ZWaveColorConverter] - NODE 3: Unknown color mode null.
18:07:56.394 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command 0,99,99
18:07:56.394 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become 0,99,99
18:07:56.395 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,96,95 to 0,99,99
18:07:56.396 [WARN ] [nternal.converter.ZWaveColorConverter] - NODE 3: Unknown color mode null.
18:07:56.595 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command 329,99,99
18:07:56.596 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become 329,99,99
18:07:56.596 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,99,99 to 329,99,99
18:07:56.597 [WARN ] [nternal.converter.ZWaveColorConverter] - NODE 3: Unknown color mode null.
18:07:56.798 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command 290,99,99
18:07:56.799 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become 290,99,99
18:07:56.800 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 329,99,99 to 290,99,99
18:07:56.803 [WARN ] [nternal.converter.ZWaveColorConverter] - NODE 3: Unknown color mode null.
18:07:57.002 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' received command 289,99,99
18:07:57.002 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' predicted to become 289,99,99
18:07:57.003 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 290,99,99 to 289,99,99
18:07:57.007 [WARN ] [nternal.converter.ZWaveColorConverter] - NODE 3: Unknown color mode null.
18:07:57.499 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 289,99,99 to 0,0,0
18:07:58.568 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,0,0 to 0,0,100
18:07:58.568 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'TestLight' changed from 0,0,0 to 0,0,100
18:07:58.796 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'ZWaveNode003FGRGBW442RGBWCONTROLLER2_ColorControl' changed from 0,0,100 to 0,0,0
18:07:58.796 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'TestLight' changed from 0,0,100 to 0,0,0

Thank you for any help you can give me.

Also I did search and read through all the other Fibaro posts that I could find that seemed relevant to RGBW and I found a few that looked like they might be related, but I couldn’t figure out what to do with any possible solutions that came out of all those topics, unless I just over looked it or didn’t understand enough about what I was reading. So hence why I am now posting for myself. Hopefully I’ve included enough information.
Other topics that I searched:

Fibaro RGBW Controller, really independent inputs and outputs possible?

Tanks for your quick response. I think I will contact FIBARO for clarification now and inform you about the result here.

Fibaro Dimmer2 turning off automatically, after a few seconds

Hi, Hope someone will be able to help me troubleshoot and issue I am having with a Fibaro Dimmer 2, fibaro_fgd212_03_005. Whenever I turn on the light, either via the switch or via openhab. The light comes on for a couple of seconds and then turns off again. I have multiple dimmer2 but it is only this one that is causing me issues. I have a fibaro bypass installed on this light. I have attached my openhab.log file here with an example, it is z-wave node 10 that is the issue. new 1.txt (73.8…

Fibaro Dimmer 2 and RGBW Z-Wave modules for sale

Power I don’t know, but frequencies depend on where you live for sure: Frequency in MHz Used in 921.4 ; 919.8 Australia, New Zealand, Malaysia 919.8; 921.4 Brazil 868.40 ; 868.42 ; 869.85 CEPT Countries (Europe and other countries in region), French Guiana 919.8 ; 921.4 Chile, El Salvador, Peru 868.4 China, Singapore, South Africa 919.8 Hong Kong 865.2 India 869 Russia 916 Israel 920 - 925 Taiwan 922 - 926 Japan, Taiwan 920 - 923 Thailand 919 - 923 South Korea 9…

Fibaro FGD212 dimmer reports dimmer update, not processed in OpenHab

That is an AV configuration issue then.

[ZWave] Fibaro FGRGBW-442 RGBW CONTROLLER 2 fails on initialization

Thanks a lot! I used color_color instead of color_color1. Now I can set colors. The only thing left is how to control the W channel manually. Using switch_dimmer5 didn’t work for me. Anyway, you’ve been a big help, @stefan.oh! Thanks again!

Fibaro Dimmer unresponsive first click problem

I have a Fibaro ZWave dimmer that seems unresponsive on first click, or actually just doesn’t turn the light on. 0-lights off, hasn’t been touch for a while. 1-first click does nothing (but think it sets its state to 1) 2-does nothing(but actually I think it’s setting the state back to 0) 3-turns the light on. Could this be because I’m running on a 2 wire system? My friend actually has the same problem, but with Domoticz, so I think this is a hardware problem. Anyone have a fix for this? …

[HomeKit] Fibaro RGBW Dimmer with openHAB homekit

Hi there, I’m currently trying to get a colorwheel into the Home App. I always left the config on “Dimmer” Dimmer SwitchDimmer_RGBWWohnLicht "RGBW Dimmer" (EG_Esszimmer) {homekit="Lighting.Brightness",channel="zwave:device:xxxxxxxx:node22:switch_dimmer"} Colorwheel should be possible with “Color” - no chance till now! Tried configs without success: Color ColorColor_RGBWWohnLicht "RGBW Farbe" (EG_Esszi…

Fibaro RGBW2 and Color Picker showing wrong state

Maybe it’s a problem of the color picker, not the Fibaro RGBW. Set color and brightness in color picker: [image] GF_MasterBedroom_Light_Bed changed from 112,87,100 to 113,88,49 Press Button to turn off light [image] Item ‘GF_MasterBedroom_Light_Bed’ received command OFF GF_MasterBedroom_Light_Bed predicted to become OFF GF_MasterBedroom_Light_Bed changed from 113,88,49 to 113,88,0 gLightGF_MasterBedroom changed from ON to OFF through GF_MasterBedroom_Light_Bed GF_MasterBedroom_L…

Problem with Zwave + Fibaro RGBW-Controller

Hey, you were right. The Color is correct but the Brightness not. But this is only with the Colorpicker. When i use: sendCommand(new HSBType(new DecimalType(18), new PercentType(87), new PercentType(37))) it works perfectly! But there is also an Error in the Feedback from the Controller. For Example you choose Red as Color the Controller changed to Red (with 100% Brightness) but the Feedback is an completely other Color, so the Colorpicker jumps around. I will post this as desired @ Github …

Also: I followed the wiring diagram that comes with the Fibaro documentation for the RGBW LED strip, with one minor exception, I didn’t wire any switches to the IN1, IN2, IN3 or IN4 inputs.
So the wiring diagram is pretty basic. 12VDC IN, GND, Red, Green, Blue, White.

[SethEden (Seth Hollingsead)]

Could this be the problem?

Zwave database update (ZV9102FA-CCT) Unknown color mode null - missing "colorMode=RGB"

Hi All, I have a problem with a z-wave item. It’s an RGBW light strip controller. When I try and change the colour it states NODE 43: Unknown color mode null After a bit of searching I think I understand the issue. Correct me if I’m wrong but it appears that the “colorMode=RGB” is missing from the following database: Pretty much the same issue as this [SOLVED] Inovelli LZW42 zwave RGB bulb Anyway I’ve registered myself on OpenSmartHouse and tried to update but I cannot do it. I wonder if @…

If it is, I’ve no idea what to do about it. I may be a software engineer, but the whole OpenHAB back end is currently a complete black box to me.

[rlkoshak (Rich Koshak)]

@SethEden

This is the configuration settings that I see.

I think it will be more helpful to click on the “Code” tab in MainUI for this Thing and post that. Use code fences

```
code goes here
```

The fact that you are seeing all this stuff indicates that the device is properly identified so it’s probably not a database problem.

Usually you’ll want the Association Group to be the Controller unless you know what you are doing.

Next it might be helpful to understand the difference between updates and commands and the behavior of autoupdate.

Updates just change the state of an Item. These do not usually go out to the actual device to cause an action to occur. A command, on the other hand does go out to the device to cause something to happen. Some important things to note:

• A Command is not always a State. For example, one can send an INCREASE command to a Dimmer Item. A Dimmer can never have the state INCREASE, only a PercentType (integer between 0 and 100). The binding will get that INCREASE command and determine what needs to be sent to the device. Eventually the Item will change state to reflect the change caused by the command.

• There can be some time between a command and the corresponding update to the Item.

• There is a feature for Items that is turned on by default called autoupdate. When autoupdate is set to on, OH will predict what state the Item will become and update the Item for you independently from what the actual device did. If you turn autoupdate to false (can be set as metadata on the Item) the Item itself will not change state in response to a command until the actual device reports back through the binding that it’s reached a new state.

Based on the logs posted it looks like what is happening is a new HSB is commanded to the light. Autoupdate is predicting the Item’s new state and updating it. The binding is saying “nope, I can’t do that” and consequently the binding is setting the Item back to 0,0,0. Is the bulb ever actually turning ON?

@SethEden

If it is, I’ve no idea what to do about it. I may be a software engineer, but the whole OpenHAB back end is currently a complete black box to me.

This could be the same problem. Looking at the database entry for this device indicates that there was an update or something last May 8th. What ever that update was it appears to only be available in the snapshots right now. Based on the date I think it should be included in OH 3.1 M5 so you can try an update to that version and see if that works.

I think there have been some breaking changes since 3.0.2 and 3.1 M5 which will make the new binding not work on 3.0.2 so you’ll have to upgrade to get what ever changed.

If after the upgrade it still doesn’t work, you’ll want to put the binding into trace or debug level logging (see the bottom of the Zwave binding docs for how) and collect detailed logs.

[SethEden (Seth Hollingsead)]

@rlkoshak

• A Command is not always a State. For example, one can send an INCREASE command to a Dimmer Item. A Dimmer can never have the state INCREASE, only a PercentType (integer between 0 and 100). The binding will get that INCREASE command and determine what needs to be sent to the device. Eventually the Item will change state to reflect the change caused by the command.
• There can be some time between a command and the corresponding update to the Item.

Thank you for this additional context information! I’m learning here!!

@rlkoshak

There is a feature for Items that is turned on by default called autoupdate. When autoupdate is set to on, OH will predict what state the Item will become and update the Item for you independently from what the actual device did. If you turn autoupdate to false (can be set as metadata on the Item) the Item itself will not change state in response to a command until the actual device reports back through the binding that it’s reached a new state.

Ok I will try to adjust that and see if I can get a change in state to persist.

@rlkoshak

Is the bulb ever actually turning ON?

No it is not turning on, no matter what color or switch setting I try to change. The only way I can get the LEDs to turn on any colors or white is to unwire the Fibaro device completely from the power circuit and then wire the LED strip directly to the power supply.

@rlkoshak

Looking at the database entry for this device indicates that there was an update or something last May 8th.

Interesting that this happened on May 8, that’s my birthday! LOL

@rlkoshak

I think there have been some breaking changes since 3.0.2 and 3.1 M5 which will make the new binding not work on 3.0.2 so you’ll have to upgrade to get what ever changed.

Sure I will try and update. I also talked with the Fibaro support so they gave me a few ideas to try like trying another device and also emailing them some pictures of the device and the wiring diagram I’m using. I’ll make a list of attack items to try and solve this problem and update here when done. Thank you @rlkoshak for your feedback and information!!

[SethEden (Seth Hollingsead)]

I was able to get the Dimmer Item to control the LED strip through the Fibaro controller:

However, I’m still having trouble with the RGB portion.
Here is the code for the Fibaro thing:

UID: zwave:device:7bebfa0bd9:node3
label: "Z-Wave Node 003: FGRGBW-442 RGBW CONTROLLER 2"
thingTypeUID: zwave:fibaro_fgrgbw442_00_000
configuration:
  group_9: []
  group_8: []
  config_154_4_00FF0000: 255
  group_5: []
  group_4: []
  group_7: []
  group_6: []
  config_30_4_000000FF: 0
  group_1:
    - controller
  config_32_4_00FF0000: 255
  group_3: []
  group_2: []
  config_152_2: 3
  config_150_1: 0
  config_33_4_0000FF00: 0
  config_155_4_7F000000: 0
  config_33_4_000000FF: 0
  config_154_4: -1
  config_156_4: 1667457891
  config_64_2: 0
  config_41_1: 15
  config_20_1: 2
  config_31_4_000000FF: 0
  config_156_4_00FF0000: 99
  config_62_2: 3600
  config_22_1: 2
  config_43_1: 15
  config_34_4_00FF0000: 255
  config_34_4_7F000000: 4
  config_32_4_000000FF: 0
  config_1_1: 0
  config_155_4_00FF0000: 0
  config_30_4_0000FF00: 0
  config_31_4_0000FF00: 0
  config_33_4_7F000000: 2
  config_66_2: 3600
  config_154_4_7F000000: 127
  config_32_4_0000FF00: 0
  config_154_4_000000FF: 255
  config_154_4_0000FF00: 255
  config_30_4_00FF0000: 0
  config_32_4_7F000000: 1
  config_151_2: 3
  config_33_4_00FF0000: 255
  config_157_1: 0
  config_155_4: 0
  config_42_1: 15
  config_31_4_7F000000: 5
  config_156_4_7F000000: 99
  config_31_4_00FF0000: 255
  config_34_4_0000FF00: 0
  config_35_2_0000FFFF: 600
  config_65_2: 10
  config_156_4_000000FF: 99
  config_21_1: 2
  config_63_2: 5
  config_40_1: 15
  config_156_4_0000FF00: 99
  config_34_4_000000FF: 0
  group_10: []
  config_30_4_7F000000: 0
  config_155_4_000000FF: 0
  config_155_4_0000FF00: 0
  config_23_1: 2
  node_id: 3
bridgeUID: zwave:serial_zstick:7bebfa0bd9

I’m not sure what else I could be missing? Any other thoughts?
When I set the color RGB values it doesn’t reset them immediately any more, so updating to the 3.1M5 version seems to have solved that problem indeed.

Another interesting thing is that even through I have used the Dimmer - Point>Control to turn on the LED white strip lights, the value still shows as “0”. I’m not sure why that is or if it’s related to the issue I’m having with the Color Control.

Any ideas would be helpful!! Thank you again!
Cheers
~Seth

[rlkoshak (Rich Koshak)]

@SethEden

When I set the color RGB values it doesn’t reset them immediately any more, so updating to the 3.1M5 version seems to have solved that problem indeed.

But the light still isn’t turning ON or changing color?

@SethEden

Another interesting thing is that even through I have used the Dimmer - Point>Control to turn on the LED white strip lights, the value still shows as “0”.

That may or may not be relevant. Not all lights report back to the controller when they’ve been changed. For those that do, the Association Group needs to be the controller.

You’ll need to generate and gather some logs. Put the binding into debug logging then gather openhab.log, events.log and zwave.log (if you configure it to log out to a separate file) around when the commands are sent.

[SethEden (Seth Hollingsead)]

I think I finally figured out how to make it work. Apparently the Thing itself needs all the correct channels to control the different RGBW colors.

I guess once I setup all the dimmer channels then I will need to setup a color control that will bind all of them and allow color selection from a full color wheel and just make sure everything is all bound together. I remember hearing about this earlier in an OpenHAB tutorial I’d seen years ago.
I’ll give it a try and update here. Thanks again for everything!!

[SethEden (Seth Hollingsead)]

Ok this is actually enough for me to validate the LED strips work and also the Fibaro controllers work, which was my main objective up to this point. So I’m going to go and test all my new hardware, then install it and much later I will come back and learn more about configurations and how to make it all work nice in OpenHAB. I just want to make sure all the money I’ve blown on this hardware isn’t wasted on broken parts. Thanks again!!

[rlkoshak (Rich Koshak)]

It is possible to develop a great deal of this configuration without the physical hardware. That’s the beauty of the layer of abstraction provided by Items. You can create a whole model for your home automation without any actual physical devices. So don’t feel like you have to wait if you don’t want to.

[SethEden (Seth Hollingsead)]

Yes I did see that you can build a model and I might play around with that a bit more to help me get through the learning curve. But I do need to stay focused on the testing of these devices before the return period runs out in 30 days. After that I’ve got to get the installation complete because I’ve got more parts arriving in another week and that will need more testing and more assembly. Once everything is installed and integrated then I think I’ll have some extra time and space to work on building out the controls and interface better. This is my first and only and big smart home project. Its all about my home office upgrade / custom gaming desk with support for 11 monitors and HOTAS flight simulation setup.