Tim Messerschmidt

The component should also define a `DOMAIN` as listed [here](https://developers.home-assistant.io/docs/en/creating_component_index.html). Furthermore, state updates are handled differently [now](https://goo.gl/Nvioub): ``` Updating state for media_player.xbox_one () took 0.699 seconds. Please report platform to...

It needs to be `__init__.py`

Check out my comment above. You may have to define a domain, too. Just use `xbox_one` as value.

Interesting -- I didn't make these changes and it runs flawlessly on 0.92.1 for me. Will see if I can change volume when I am back home.

In the same vein, it may be useful (and actually necessary for this feature to work) to implement placeholders -- e.g. being able to space out entities as you want.

Better late than never. I'd also be interested -- would even consider buying a pre-assembled unit ;-)

Pardon my ignorance, but isn't this something that can be handled by disabling manual polling for the integration? This was added in [2021.6](https://www.home-assistant.io/blog/2021/06/02/release-20216/#disable-polling-updates-on-any-integration). It does come with the downside that...

> Polling switch is by car. The HA feature is per integration. Some people have multiple cars. Yeah, I get that downside. It's not great for people with multiple cars...

I countered that by implementing a template sensor that leverages the switch and the attributes it populates while in operation: ``` mr_coffee_current_progress: friendly_name: 'Progress' entity_id: switch.mr_coffee unit_of_measurement: '%' value_template: >...

Got it. Thanks!