I guess to me this still comes down to wanting something native and simple. What i would love is a system that worked something like this:
Enable this new feature if you want to be notified if any entity ever goes offline/unknown. (maybe this could go into “repairs”? i dont know if that is the right spot.)
right off the bat, you will likely be notified of a number of entities in those states. you would get to remediate them, and then be given the easy option to “ignore” the rest. then you would be in a steady state where you are confident things will work as expected. in my case, remediation was a mix of deleting old entities from experiments, power cycling some devices, and and plugging a device back in that was unplugged in my garage.
if something goes offline for a good reason, ( i unplug a lamp to re-arrange a room to do some painting) then i would love to be able to ignore that issue for a day/week/etc…
maybe a lux sensor on a device starts acting up and routinely shows up as unknown, i get to choose to troubleshoot that device, maybe buy a replacement, or decide that i dont care about that light sensor at all, and i would disable the entity, or simply permanently ignore it from this alerting if i wanted to keep the entitiy for some reason.
For me, i have 2000+ entities, and im only ignoring ~100 of them. if any of the remaining 1900 entities ever go offline/unknown, someone in the house is probably going to have a bad experience with HA.
to be clear, i dont want to have to look at a dashboard to find issues, the main goal of this WTH is for the system to be proactive and easy to use. (and that means not having to write or re-use someone elses complex yaml+jinja)
to sum it all up, i know there are ways to to basically get what i want here with enough tinkering, but my point is… why isnt it there by default? If someone spends the time/money/effort in setting up a smart home device, I think we can bet that they want to know if it isnt working,