Of course, I only meant that for testing purposes.
So I did a 6hr wake up overnight, pulled battery (showing 100% on hub), and had a delayed battery 80% for 6hrs. The delayed event posted at 2:15AM and the device got marked offline at 2:38AM. So it seems it only uses incoming reports from the device to determine online status.
2 Likes
@nayelyz a question for the engineering team, when using ZigBee devices I assume that HubCore health check uses the PollControl cluster and CheckIn to see if the device is alive. What happens when a ZigBee device doesn’t support the PollControl cluster? I’m facing an issue with some Zigbee device which don’t support the PollControl cluster are being marked offline after a few hours. The issue is that I the reporting on this is fixed (not configurable) so I can’t adjust the time period for regular updates (like IASZone or PowerManagement), I just need to wait until the device sends a report which can be once evert 8 hours or so. What can I do to avoid having HubCore mark the device offline?
Hi, @RBoy
The engineering team mentioned the PollControl cluster isn’t used for the health check interval.
In this case, what you can do is set a schedule to send a readAttribute command to the device in a defined interval by a setting/preference, in the case of Zigbee it should respond shortly after even if it’s sleep. Unlike Z-Wave which turns off its radio.
I tried that but the device doesn’t to respond to requests. It’s a battery operated leak sensor. It only responds to requests when it is manually woken up. Once it goes sleep It just sends IAS reports at a pre determined interval. My guess is that because it doesn’t support the PollCuster it doesn’t support the CheckIn command which is what’s required by Zigbee devices to wake up and get into FastPoll mode to receive the pending commands from the hub. In this instance, can the team suggest something to prevent the device from being marked offline?
Sorry for the delay, I was OOO, I just asked the team, I’ll let you know their feedback.