I’ve seen situations where this occurs and can be remedied by using a Routine to set/change some value in the settings. I have a virtual device that I keep around for various scenarios, including this one. I just create a Routine like “When virtual device turns on, then ‘set something on misbehaving device’”.
Awesome Idea, however in this situation, the devices are water sensors…so there are no parameters I can change via routine. I just tried this, and when I selected the “then” option in the routine, all the water detectors don’t even show up as an option to select. They only show up in the “if” section.
The zse42 has a default wake up of 12 hours and supports changing the wake up interval (according to the manual anyway.) I’m surprised the official Zooz driver doesn’t have a preference for changing it. Kevin’s drivers usually do.
As it’s a zwave sleepy device, doing a refresh (pull down in the app) really does nothing. The device isn’t listening even if the hub sent out any “send me all your current data” type messages.
The device should sync any parameter or configuration changes on wake up. That’s what the counter is trying to show, how many are pending.
Some attributes may not be refreshed every wake up, only when they change. For instance, battery level.
However, drivers should set an initial value for all attributes on the device include (or after a driver change). That way the UI doesn’t complain that “the device hasn’t updated all of its status information yet” until an update from the device (unsolicited or during wake up).
Rebooting the hub wouldn’t help solve the issue. Doesn’t hurt anything either.