@dnickel, the (incomplete) list of community drivers that support the healthStatus attribute can be found here:
I should probably edit or rephrase the first sentence in the top post to clarify that the Hubitat platform only displays an offline icon on the dashboards and certain device list pages. Note that the built-in system drivers from Hubitat do not support the healthStatus attribute.
What Aqara or Xiaomi devices do you have? Most of them should have a dedicated community driver with health status. Please check the links in the second post of the thread linked above. Personally, I am using the modified Markus's drivers for my Aqara buttons and contact sensors :
Personally, I don't use the "Xiaomi Aqara Mijia Sensors and Switches (w/ healthStatus)" driver (the one you refer to), as I think that combining so many different device capabilities in a single driver is not a very good idea.
If this driver is not updating properly the healthStatus attribute when the device has stopped sending any Zigbee messages to the hub, the problem may be in the driver code, so we need to look at it. The first thing to look at is the deviceHealthCheck periodic job - it is responsible for changing the heatlhStatus to offline. Do you have this scheduled job running? (see the sample screenshot above)