Paulus Schoutsen

I wouldn't want to return just the device name. Probably something like `device(entity_id)` returning a [device registry entry](https://developers.home-assistant.io/docs/device_registry_index#device-properties)

I agree that an unavailable reason would be a nice addition. For the unavailable attributes, I think that it should be good to keep any attribute that _describes_ the entity...

I think that this is the wrong approach. Groups can group more things than just binary sensors, to fallback to binary sensor text rendering would be weird. To look at...

I think that the system is behaving as expected. I think that if Tesla doesn't want to update, they should mark themselves as unavailable until they want to update. However,...

When using the name "toggle", the generic service `homeassistant.toggle` will pick it up too.

Good idea. Then we can also implement syncing with Alexa to do lists 👍 Things that come to mind: Support for different lists. Add, Update, Remove, Clear completed. Move (up/down/indent/unindent?)

If `set_state` would be added, people would also expect to be able to see always every attribute in the light state, even if it is not currently in use. So...

@mickdekkers I don't think that we should add code to the core to make a specific use case (only control via HA) work better while making other use cases more...

What you're proposing is a new automation component with device and integration specific triggers instead of triggers based on events/states.

Sometimes sync code will need to be implemented in async because it needs to use sleep or locks, which we don't want in sync-land.