WTH doesn't devices that silently drop offline raise an issue or TODO?

Month of "What the heck?!"
, , , ,
7

For deleted devices/integrations, we have Spook (awesome! but for advanced users)!
For offline devices, I’ve been using many tools. For example:

type: custom:auto-entities
card:
  type: entities
  title: Offline (top 5)
  state_color: false
filter:
  include:
    - state: unavailable
      integration: mqtt
  exclude:
    - entity_id: sensor.oral_b_*
    - entity_id: binary_sensor.*_update_available
    - entity_id: sensor.*_battery
show_empty: false
sort:
  method: last_changed
  reverse: true
  first: 0
  count: 5

Again, it requires HACS/MQTT add-ons and knowledge about how Home Assistant works. But it works pretty well, and it’s simple. I’ll work something different to create TODOs based on, for example, being offline for more than 3 hours, based on devices class, or even with include/exclude rules (again, an automation).

More examples I’m using / used to use: