* Fix late group platform registration
* use a callback instead
* Run thread safe
* Not working domain filter
* Also update if a group has nested group's
* Only update if the siingle state type key could change
* Avoid redundant regisister hooks
* Use set, add comment
* Revert changes
* Keep callback cleanup const
* Cleanup after dependencies
* Preimport and cleanup excluded domains
* Revert test changes as we assume early set up now
* Migrate alarm_control_panel
* Migrate climate
* Migrate cover
* Migrate device_tracker
* Migrate lock
* Migrate media_player
* Migrate person
* Migrate plant
* Migrate vacuum
* Migrate water_heater
* Remove water_heater group_pre_import
* Use Platform enum if possible
* Also use platform enum for excluded domains
* Set registry to self._registry
* move deregistering call back hook to async_added_to_hass
* Add comment
* Do no pass mutable reference to EXCLUDED_DOMAINS
* Remove unneeded type hint
Remove group integration platforms that use the default
There is no need to register platforms that use the defaults
as the group code already uses STATE_ON/STATE_OFF when there
are no on/off states in the GroupIntegrationRegistry
These update call the storage collection async_update_item
which never suspends so they can finish synchronously without
having to be scheduled on the loop when run_immediately,
which schedules the task eagerly is set
Nothing was being awaited here so there was no need to create
a task per person at the start event.
The async_update_config coro remains since its required
by the collection but is now a wrapper around a callback
_async_update_config
* Move definition of attributes excluded from history to entity classes
* Revert change which should be in a follow-up PR
* Fix sun unrecorded attributes
* Fix input_select unrecorded attributes
* Add common translations
* Add common translations
* Add common translations
* Add common translations
* Add common translations
* Add common translations
* Add common translations
* Add common translations
* Complete migration of persistent notifications
Persistent notifications are no longer stored in
the state machine and no longer fire events
* Complete migration of persistent notifications
Persistent notifications are no longer stored in
the state machine and no longer fire events
* fixes
* fixes
* fixes
* ws test
* update tests
* update tests
* fix more tests
* fix more tests
* more fixes
* fix
* fix person
* fix person
* keep whitelist
* use singleton
* Support marking an assist pipeline as preferred
* Adjust
* Revert unneeded change
* Send preferred pipeline id in pipeline list
* Don't use property functions for the preferred pipeline
* Add websocket type hints in components
* Adjust
* Apply suggestion
Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
