I personally wish unavailable was separated out and made into an additional property on the state object in combination with a new “device/entity online/offline” trigger. That would essentially remove all need to check for to/from unavailable states while still being able to do everything that’s available now. I.e. when this entity goes offline, when this entity comes back online, when this device goes offline, etc. We’d still have unkown as a possible state, but that would only be for a few types of entities that have no known state during startup or don’t have an assumed state during startup. It would really alleviate a lot of random issues with automations without needing template conditions or needing any UI changes.
4 Likes