Markus

can you post the code/yaml of getting the `unavailable` state? you may using a non documented HA API feature?

ok, then the HA API docs are incomplete :O looks like esphome currently has no component `unavailable` hadling internaly. https://github.com/esphome/feature-requests/issues/1568 so there is not generic state I can set for...

feel free to test. and yes `unavailable` and `unknown` are seperate. but the state `unavailable` forces `unknown` to be true too. `publish_state` will be called on change to `unavailable` and...

yay, had the same idea. the question big question is its a good idea to add the unavailable and unknown bools to all entities of esphome as a optional feature,...

no really adding the bools to the EntityBase class is easy and deduplicates a lot of code. I for sure will not implement the `unavailable` and `unknown` in one go...

interesting had a short look and did not see any handling of the `unavailable` and or `unknown` state in home assistant.

added trigger support e.g.: ```yaml binary_sensor: - id: !extend btn_boot on_click: then: - if: condition: - entity.is_unavailable: my_cool_cover then: - logger.log: my_cool_cover unavailable - if: condition: - entity.is_unknown: my_cool_cover then:...

I had no problems in my testing, the HA API sends a update for every 1% in may tests. look like your code does "optimistic updates" e.g. your `control` function...

I dont see a problem with a shared class for all homeassistant sub components. will makes thinks easier in the future. at least in my cases there is no delay...

I hate to ping people but any feedback from the esphome Team for thes PR is highly appreciated.