Nothing definitive to report as of yet but changes at least for some identified device health issues are in discussion and development. @carter.swedal has been doing the legwork on that front and may be able to provide some more information after we pin things down. The fixes lined up may not work for all devices and we are looking at both specific device fixes (e.g. configuring the device to do periodic reports of other attributes if the ones configured today are not working according to spec) as well as improving some of the inferences made by the core protocol code used to automatically determine the expected reporting interval and fallback “ping” behavior for devices.
For the devices not working are other attributes (if supported) such as battery or temp reported at all? Sorry if these devices don’t support those, I’m being lazy and not looking up the specs as I don’t have those particular devices in my home or test setups. Not receiving the attribute at all does seem like a configuration problem for those devices.