I've had MANY instances of paired / provisioned devices, on the device list, which I have NOT intentionally disabled, dropping their connection to the Zwave, zigbee or wifi network ie no longer being connected. I usually don't know about this until a rule fails. To address this, I've deployed a community app that sends a daily notification of devices the hub has not heard from, but this is an imperfect solution at best.
I am guessing @calinatl is asking for heartbeat or health check type of information.
It may sound like a simple request, but there are many old threads around here that would demonstrate it’s anything but.
It’s also unrelated/off topic from the feature requested in the OP and the rest of the discussion in the thread.
Not exactly sure what heartbeat or health check info is, but it sounds good. I'm not familiar with the threads explaining why that is difficult to implement. Nor do I think my comment is unrelated/off topic from the OP's feature request, although you clearly think differently.
OP asked for a column on the devices page to show HOW the device is connected to Hubitat - ie via which protocol. My logic, and my resulting comment is, that if the powers that be consider such a column, they also consider using the same screen real estate to provide further information about the device connections - ie not merey HOW the device is supposed to be connected to Hubitat, but IF it actually is still connected to Hubitat.