Zwave-JS weird behaviour with Fibaro FGRGBW - Help

[sender]

I have 1 lastly added device (ID80) which worked fine for over 8 years in a Vera system. I excluded it from Vera, included in Zwave JS and get:

Now when I control the switches (dim or on/off) of the RGBW controller they quickly become unavailable and come back and at that time the entire Zwave JS integration is reloaded! All zwavejs devices become “unavailable” a moment. Since I have some toggle actions via node red and they are instantly triggered after controlling the RGBW switch/dimmer. I have tried to find what can cause this or how it happens but I am limited in my troubleshooting skills. I captured the following logs of me switching a button of the RGBW and then it reloads. I think after the reload the logging stops… What is causing this weird behavior?

2021-11-19T13:13:11.567Z DRIVER » [Node 080] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      16
                                  └─[MultiChannelCCCommandEncapsulation]
                                    │ source:      0
                                    │ destination: 1
                                    └─[MultilevelSwitchCCSet]
                                        target value: 255
                                        duration:     default
2021-11-19T13:13:11.577Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-11-19T13:13:11.652Z DRIVER « [REQ] [SendData]
                                    callback id:     16
                                    transmit status: OK
2021-11-19T13:13:14.248Z DRIVER « [Node 080] [REQ] [ApplicationCommand]
                                  └─[MultiChannelCCCommandEncapsulation]
                                    │ source:      2
                                    │ destination: 2
                                    └─[MultilevelSwitchCCReport]
                                        current value: 99
2021-11-19T13:13:14.301Z DRIVER « [Node 080] [REQ] [ApplicationCommand]
                                  └─[MultiChannelCCCommandEncapsulation]
                                    │ source:      3
                                    │ destination: 3
                                    └─[MultilevelSwitchCCReport]
                                        current value: 99
2021-11-19T13:13:14.328Z DRIVER « [Node 080] [REQ] [ApplicationCommand]
                                  └─[MultiChannelCCCommandEncapsulation]
                                    │ source:      3
                                    │ destination: 3
                                    └─[MultilevelSwitchCCReport]
                                        current value: 99
2021-11-19T13:13:14.389Z DRIVER « [Node 080] [REQ] [ApplicationCommand]
                                  └─[MultiChannelCCCommandEncapsulation]
                                    │ source:      4
                                    │ destination: 4
                                    └─[MultilevelSwitchCCReport]
                                        current value: 99
2021-11-19T13:13:14.501Z DRIVER « [Node 080] [REQ] [ApplicationCommand]
                                  └─[MultiChannelCCCommandEncapsulation]
                                    │ source:      5
                                    │ destination: 5
                                    └─[MultilevelSwitchCCReport]
                                        current value: 99
2021-11-19T13:13:14.545Z DRIVER « [Node 080] [REQ] [ApplicationCommand]
                                  └─[MultiChannelCCCommandEncapsulation]
                                    │ source:      5
                                    │ destination: 5
                                    └─[MultilevelSwitchCCReport]
                                        current value: 99
2021-11-19T13:13:14.593Z DRIVER « [Node 080] [REQ] [ApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 99

I tried other setting for paramter 14 from below:

RGBW Controller - Z-wave controller | FIBARO Manuals

But that changes nothing

[sota (Pat Rooney)]

I just finished migrating to Z-WaveJS and I’m experiencing exactly the same problem. My 30+ other devices came across fine (I rebuilt my Z-Wave network from scratch), but these are these are all that’s left to fix.

I don’t think parameter 14 is relevant, that seems to be a setting for the switches that control the lights.

Have a look at parameter 6, I seem to recall that had to be changed when using the old Z-Wave integration.

[sender]

Parameter 6?

[sota (Pat Rooney)]

Yes, from memory I think it had to be set to Normal (RGBW) - COLOUR_CONTROL_SET. It might be worth a try, I’ll look at it myself tomorrow if I have time.

[sender]

Please let me know before I do so. Edit: did it… nothing changes… entities stay the same…

[sota (Pat Rooney)]

Yes, same here. I also did a factory reset on the device and re-included it. Still no joy.

When I get a chance I’ll log an issue on GitHub.

[sota (Pat Rooney)]

I have opened an issue on GitHub and linked to this post - https://github.com/zwave-js/node-zwave-js/issues/3787

[sender]

I have excluded it and replaced it by a shelly rgbw2 with eshome flashed…

[sota (Pat Rooney)]

I may go a similar route, but I would like to make an attempt at fixing this. I already have a growing collection of failed HA projects without adding these to it!

[sota (Pat Rooney)]

As a follow up, I sent the two FGRGB 441 controllers back to Fibaro Poland to have the firmware updated to version 27.27. They don’t charge for this service, but you have to pay shipping to send them - €35 in my case. After reinstalling them, they now work perfectly, so it was definitely a firmware bug. It crazy that they have to go back to the manufacturer to have the firmware updated, it certainly will put me off buying any more Fibaro devices. Screenshot of working device for reference:

[Goldwing]

Correct (in my case)
I have 3 Fibaro RGBW controllers (411’s), 2 of them with 25.25 firmware and one with 22.22 firmare
After i set the parameter 6 to 2 in Z-WaveJS it works like a charm. (the 25.25 firmware version)

Oh, and don’t forget to do a reload of the z-wavejs integration in HA.

With the 22.22 firmware it makes no difference, changing parameter 6 to 2 or 1 still reloads the z-wave network.
I found a home automation shop nearby that has a HC3Lite and he agreed to upgrade the RGBW’s to 27.27 for me.

[davinci]

This bullshit is happening to me as well. I might have changed/reset some parameters. I am on firmware 22.22. This was working for years and now it doesn’t. What a crap.

What parameters did you finally set?

Nevermind, I probably just switch to Gledopto Controller Zigbee 3.0 RGBW… Tired of Fibaro and their weird firmware philosophy.

[Goldwing]

Solution here was upgrading the firmware to 27.27, i mailed Poland but they would only update the firmware of devices that were sold by official Fibaro resellers (apparently Amazon isn’t one)
So i was stuck with 6 RGBW controllers running firmware 22.22 or lower, and all had problems in z-wavejs.
I decided to buy a used (and cheap €50,00) Fibaro HC2 from Marktplaats (dutch eBay) and updated all my RGBW’s.

If anyone from the Netherlands has the same problem, I’m willing to upgrade your firmware for free, you only pay for the shipping (shipping is your risk)

[sota (Pat Rooney)]

Changing parameters won’t help you, I’m afraid. As I discovered, the only fix for 22.22 firmware is to get it upgraded or else bin it.

[davinci]

I decided to trash them. The screws broke anyway.

In the future, I prefer open systems that allow to fix bugs in the firmware.