Heartbeats
-
I wonder if a 'virtual child' of the sensor might be a solution? Just define a second child of the node that periodically sends the opposite status. It would simply be defined in the sketch on the sensor, not tied to actual hardware. First interval, it sends 'true' or 'open' or 1, next interval it sends 'false' or 'closed' or 0. Since it's programmed to change every interval, looking at the last update of the virtual child will let you know the sensor is functional or not.
Yes, this is already possible today. Downside is that the user has to keep track of what other sensors (entities) this information applies to. The
node_idis available among the state attributes so that will be a help. -
Seems the node id would server that tracking need.
-
Yes, with some imagination, you could probably make a template that would match the correct criteria, and use eg for a notification.
