Simon Lamon

It starts with automations only and uses the area_id to filter. There are no entities involved beside automations. I have tried duplicating an existing automation and assigning it to a...

I've done a test run on this one and it work pretty well but I'm a bit thinking about how it will be used by home assistant users that don't...

That need some thinking. Since I'm just a voluntary reviewer I may wait for feedback from the Nabu Casa team.

Things will move faster now that core is already approved, I'll give it a review this weekend. Feel free to resolve the linting issues in the meantime.

Sounds related to the [issue](#21229) but for a different table and the code should be adapted for that table similar to #21233.

> Instead of adding a new constraint, couldn't we just add the custom integration to the block list here? > > https://github.com/home-assistant/core/blob/4721f8ef5f14690249a8a98e481528f352faf987/homeassistant/loader.py#L92-L94 It doesn't crash or cause any performance issues...

I'm going to close this one, since I don't think it appropriate to block a custom integration at this moment.

The prettier warnings are still causing the CI to fail: You can run `yarn run format:prettier` to fix.

It was part of how we passed it the backend. We do some sanitizing before passing it to the backend, and the spaces came out encoded after sanitization since spaces...

Normally, we're moving away from polymer, but it seems like the css vars are still sticking to the polymer css variables. So yes, that should be correct.