Hubitat’s HomeKit integration currently exposes cached light/switch state even when a Zigbee/Z-Wave device driver has marked the device offline via healthStatus: offline.
Please add an option for the built-in HomeKit integration to map device health/offline state to HomeKit per-accessory “No Response” / communication failure, at least for devices exposing HealthCheck / healthStatus.
This would match the behaviour of native bridges such as IKEA/Tradfri, where a mains-powered-off bulb appears as unavailable rather than showing stale state.
Which drivers are you referring to? AFAIK, there are no built-in drivers that do this. And device health status is not a listed as a device capability.
Proposals have been made in the past for the platform to support some mechanism that indicates whether a device is communicating with the hub or not.
I'm not sure if there are any built-in drivers. I'd be happy to fork some of the common drivers to do it. But the limitation appears to be the HomeKit Bridge, which as far as I can see is closed source and editable only by the Hubitat team.
HomeKit has the capability to receive a 'no response' status from a hub. I'm asking whether the HomeKit Bridge in Hubitat could please be updated to allow drivers to be able to send that event to HomeKit. (And of course add it to the documentation so that anyone interested in writing drivers can use it.)
Probably, the HE devices networkStatus (where available) can be translated to HomeKit 'no response' status. (Hopefully, also the healthStatus custom attribute used in a number of community drivers )
Personally, I'd be really grateful. I imagine a lot of other users might too. Apple Home currently shows stale status for a lot of devices if members of the family have turned a few things off at the mains, for instance.
