FGRGBW-442 RGBW Controller 2 needs to be reconfigured every 2 days

[Docraj 0]

Since upgrading to 5.140.17, I find that all my FGRGBW-442 devices stop working and "Not Configured" message shows up in the dashboard for them. Once soft reconfigured they work properly for about 48 hours and then I have to repeat the process again. I have 5 of them in my installation and this issue is with all of them (firmware 27.27). Anyone facing similar issues? Anything I should do to fix this? Any help appreciated. Thanks

[olafkatzer 5]

here also this problem. after soft reconfig it is working. i'am waiting how long.

[yves.guern 1]

I have the same problem with HC3 FW 5.130.

The problem is may be with FGRGBW-442 FW itself?

Regards,

[fingusio 12]

HC3 5.140 - 11pcs RGBW2 since 10days and no any problems...

Please login or register to see this attachment.

[pflugj 13]

Hi. 
I had about 140 devices, where 30 of them where 1st generation RGBW controller!
The more devices I added the worse it got!
Randomly after reboots some of the FGRGBW-442 devices stop working and showed up as "Not Configured"

A soft re-con works BUT it changes some of the (sub) devices Id 's and Labels.
Which is also NOT suppose to happen!!

I had even worth problems!!
These controllers eventually created GHOST association and 
switched devices randomly ON, without any visible action in the history, script or via association.

AFTER ~ a YEAR of struggling and mailing the support (at least about ~100 emails )
It turns out that the number of "1st gen RGBW" controller is causing the problem!
creating to much traffic:
here is the support answer:

Quote

About RGBW1, they are creating big Z-wave data frames, especially with so many of them like in your setup.
But those devices have ZW chipset 300 that the manufacturer Silabs is not going to improve or maintain so we can't reduce those frames.
We are still improving functions to reduce the issue from our site as much as possible.
 

So for me the ONLY solution was: Replace ALL 30 Controllers - (at my expense!!!)
After that ,THIS problem has not occurred since!
YIPPEEE

But I then I discovered a new problem!
Some of the RGBW2 controllers have push buttons, directly connected to the inputs 1-4.
A double click on the old RGBW, switched the connected output channel to full brightness.

When double clicking the buttons, connected to the new RGBW2 controllers:
the LED strip stays off
The color channel is fully increased to "255"
BUT
the "Brightness"  channel stays at "0"
 

I did some digging and found this thread in your forum:

Please login or register to see this link.

Among a LOT of other things:

Brightness disassociated from RGBW channels

With the RGBW 1, when you changed the RGB or W channel the brightness moved with it.

This was already reported in 2020!!
 

I wrote to Fibaro again last week and still NO info bout new FIRMWARE for the RGBW2!
 

cheers