Hi all, I bought a Fibaro "The Button" to use with my Christmas display. It's a cool looking button that kids love to press and I have it set up on a little stand by the road and when someone presses it, it randomly changes the lights on the house to a different effect and color scheme.
I'm using the generic button driver but the only problem is the button goes to sleep after a while and needs to be manually woken up with 4 button presses which makes it seem like the display is not working.
I see on Fibaro's website that there is a setting you can change to change the wake up period from manual to every so many seconds:
Available settings: 0 or 3600-64800 (in seconds, 1h – 18h)
Default setting: 0 (only manual wake up)
But this obviously isn't available in the generic button driver.
Anyone interested in tackling a custom driver? This button is one of a kind and kids love it so I'm sure lots of folks would get use from a custom driver.
That doesn’t sound like that is what that setting will do. That’s just when it will periodically wake up to check in with the hub (something you’ll find on every battery powered Z-Wave wave device). For some devices, this may cause the driver to send new parameters or maybe request a report of some kind or something similar -- or just note that it checked in -- but will probably not have any effect on real world functionality of device, including if it takes a while to “wake up” on its own during regular use.
EDIT: Also, the default wakeup interval is set to 12 hours by the driver by default (typical for many Hubitat drivers), not manual only. Additionally, per the description you provided, the minimum is 1 hr, not "seconds" (nor would you really want it to be less -- all these wakeups will probably drain the battery notably faster).
Thanks for clarifying that. That makes sense now that I think about it. It's unfortunate the button goes to sleep, what kind of a button needs to be woken up before you can press it!?
Is there any way to send some type of signal to the button periodically to keep it awake perhaps?
I doubt it unless the device notes that it supports FLiRS anywhere, unlikely for a device that doeesn't normally need to accept commands on battery (like blinds or locks). Is there any chance you don't have Z-Wave repeaters (or the hub) in range of this device or that it experiences frequent route changes that may cause it some confusion on wakeup? (I suspect you're only noticing no "delays" after a manual wakeup because that causes some Z-Wave traffic and lets it figure things out before your actual button event...)
No I don't see any commands that wouuld wake it either, Reading on the Fibaro forum, it seems the device is really hit and miss whether it works for people reliably as it seems to go to sleep and then need to be woken up:
I ended up finding a custom driver for the Fibaro button by @cumpstey that, by default, doesn't have the button go to sleep for much longer. It seems there is a zwave parameter, zw wake interval, for time elapsed before the button goes to sleep, and this driver has the button not go to sleep for longer