i just installed my first Fibaro RGB Controller 2 in my system and its acting strange.
Z-Wave inclusion went fine and everything got detected as it should.
i can change the color but as soon as i turn it Off the openhab item gets turnd off and on again, however the LED Strip stays off.
I do not see why i have this in the log and why its changing to 29 again.
2020-07-24 11:50:03.691 [vent.ItemStateChangedEvent] - S_LR_LEDStrip_D changed from 0 to 29
2020-07-24 11:50:02.110 [ome.event.ItemCommandEvent] - Item ‘S_LR_LEDStrip_D’ received command OFF
2020-07-24 11:50:02.122 [nt.ItemStatePredictedEvent] - S_LR_LEDStrip_D predicted to become OFF
2020-07-24 11:50:02.128 [vent.ItemStateChangedEvent] - S_LR_LEDStrip_D changed from 50 to 0
2020-07-24 11:50:03.691 [vent.ItemStateChangedEvent] - S_LR_LEDStrip_D changed from 0 to 29
2020-07-24 11:50:03.993 [vent.ItemStateChangedEvent] - S_LR_LEDStrip_D1 changed from 50 to 25
2020-07-24 11:50:03.995 [vent.ItemStateChangedEvent] - S_LR_LEDStrip_C changed from 94,92,93 to 94,92,25
2020-07-24 11:50:04.243 [vent.ItemStateChangedEvent] - S_LR_LEDStrip_C changed from 94,92,25 to 94,92,93
The “jitter” section here will give you insight into your logs.
I’m not sure how you can persuade your device to report “off” after it has settled down. Sometimes playing with poll-after-command period seems to help with zwave.
i looked into the “jitter” part and it looked like that, except that i’m not getting the right state reported in the end.
I would expect to see in the end the correct state but it’s not.
2020-07-24 12:43:32.424 [nt.ItemStatePredictedEvent] - S_LR_LEDStrip_D predicted to become OFF
2020-07-24 12:43:32.435 [vent.ItemStateChangedEvent] - S_LR_LEDStrip_D changed from 26 to 0
2020-07-24 12:43:33.997 [vent.ItemStateChangedEvent] - S_LR_LEDStrip_D changed from 0 to 34
Yes, you need to get your device to report “off” after it has settled down. Sometimes playing with command poll period seems to help with zwave, this is a Thing setting I believe.
1.5 seconds seems like it ought to be plenty of time really, you can see that effect in your events.log.
But if it isn’t for this device, then it isn’t.