I have multiple Fibaro RGBW and Zooz RGBW controllers and each of them are very slow to show commanded changes (sometimes as long as 30 seconds) I have tried the Hubitat driver, the Hubitat Beta Driver with the same results. I have excluded and re-included the devices with no improvement. The logs are not showing errors and I can see when it was created and have looked at the logs as far back as I can get the only thing that shows is a "WARN" when I disable or inable the logging. Any thoughts or ideas I can go after?
I have 4 Fibaro RGBW controllers that are doing the same thing. They can take 20-30 secs to respond or sometimes will not respond at all.
Have you tried any generic driver? I have no clue what direction to go. All of these devices where quick to respond on Vera (that’s about all I can say on that front) but just painfully slow and the family approval is taking a big hit!
@cwilberg I think I just figured part of my issue out. My two Fibaro RGBW controllers are first gen and therefore are not Z-Wave Plus devices, which may be causing the delay. I But even with the Zooz controller I still have some delay and the color picker I cannot close after picking a color I have to either refresh the page or use the back button.
@sky320 I have not tried a generic driver with them yet. I also do not know if mine are first generation or not. I'll take a look at both of those in the next few days. I do have problems when I try to change colors (especially on the dashboard tiles) where I have to close out of the color selector and try again to get them. If the color does change, it takes quite a while to reflect that change on the dashboard (30-40 secs maybe?). I've found that the first command to them to turn on or off generally goes relatively quick, but subsequent commands usually have the lag. I've tried putting a z-wave repeater nearby and doing a z-wave repair, but no change there.
@sky320 @cwilberg Up until recently, I was using the Hank RGBW driver for my Z-wave strip light controller. Seemed to work well with command changes, including Alexa.
(Am currently using/testing a beta driver for the controller I have that someone in the community has put together)
@Gnant please let me know how it works and if the dev is ok with you passing it along to those of us in need of a good driver.
The controller I am using is an RGBgenie Z-Wave plus unit. I should have been more clear. Sorry.
Edit: I mentioned the Hank driver because it did work better than the generic one for me anyway.
My Fibaro units are are version 2.5. I tired several different drivers and the Hank driver did perform the best, but still not perfect. I have them in a few groups of 2 and 4 and often one of them will fail to execute whatever I command the group to do. It's different ones each time.
2.1.8 will have a driver (generic zwave rgbww) that should work better with this controller.
@mike.maxwell for both the Fibaro and Zooz controller? Thanks for the heads up with this info also.
@mike.maxwell Thanks Mike. I'll try it once it comes out.
Neither, this one is for the RGBgenie and other non dedicated devices.
Fibaro and zooz have dedicated drivers already
@mike.maxwell thanks for the info. The drivers in Hubitat work rather poorly there is a huge delay and color picker on dashboard does not work either. I will keep searching, hope someone here will create or update the current drivers to fix these issues.
Any command delay you have isn't in the drivers...
I don't know what issues you specifically are having, but they are not driver related.
I own several of these devices, none of them have huge delays of any sort (or any delays for that matter), their response is on par with every other zwave device i have tested.
I agree with @mike.maxwell, the Zooz RGBW driver changes the color almost instantly for me and the color related status changes are only delayed by a few seconds.
The color picker is part of the dashboard/IDE and has nothing to do with the driver...
I'm also having issues as outlined here:
With the onoff status issue - I am finding that getting RM to send out a manual refresh anytime the device is used helps resolve this - but it is definitely a driver issue as it should not need to be manually refreshed
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
