* Add fan mode support to knx climate
* fix linting errors
* remove unneeded None protection from CONF_FAN_PERCENTAGES_MODES
* Update homeassistant/components/knx/climate.py
Co-authored-by: Matthias Alphart <farmio@alphart.net>
* Update homeassistant/components/knx/climate.py
Co-authored-by: Matthias Alphart <farmio@alphart.net>
* Update homeassistant/components/knx/climate.py
Co-authored-by: Matthias Alphart <farmio@alphart.net>
* Update homeassistant/components/knx/schema.py
Co-authored-by: Matthias Alphart <farmio@alphart.net>
* find closest percentage when not in fan modes
* new field for fan speed mode, max steps apply to both step and percentage
* not picking FAN_OFF when the percentage is closest to zero
* add fan zero mode to support auto mode
* use StrEnum for FanZeroMode
* change default to 'percent'
* fix mypy errors
---------
Co-authored-by: Matthias Alphart <farmio@alphart.net>
* Fix loading KNX UI entities with entity category set
* add test
* docstring fixes
* telegram order
* Optionally ignore telegram sending order in tests
because we can't know which platform initialises first
* Support DPTComplex objects and validate sensor types
* Gracefully start and stop xknx device objects
* Use non-awaitable XknxDevice callbacks
* Use non-awaitable xknx.TelegramQueue callbacks
* Use non-awaitable xknx.ConnectionManager callbacks
* Remove unnecessary `hass.async_block_till_done()` calls
* Wait for StateUpdater logic to proceed when receiving responses
* Update import module paths for specific DPTs
* Support Enum data types
* New HVAC mode names
* HVAC Enums instead of Enum member value strings
* New date and time devices
* Update xknx to 3.0.0
* Fix expose tests and DPTEnumData check
* ruff and mypy fixes
* knx entity CRUD - initial commit - switch
* platform dependent schema
* coerce empty GA-lists to None
* read entity configuration from WS
* use entity_id instead of unique_id for lookup
* Add device support
* Rename KNXEntityStore to KNXConfigStore
* fix test after rename
* Send schema options for creating / editing entities
* Return entity_id after entity creation
* remove device_class config in favour of more-info-dialog settings
* refactor group address schema for custom selector
* Rename GA keys and remove invalid keys from schema
* fix rebase
* Fix deleting devices and their entities
* Validate entity schema in extra step - return validation infos
* Use exception to signal validation error; return validated data
* Forward validation result when editing entities
* Get proper validation error message for optional GAs
* Add entity validation only WS command
* use ulid instead of uuid
* Fix error handling for edit unknown entity
* Remove unused optional group address sets from validated schema
* Add optional dpt field for ga_schema
* Move knx config things to sub-key
* Add light platform
* async_forward_entry_setups only once
* Test crate and remove devices
* Test removing entities of a removed device
* Test entity creation and storage
* Test deleting entities
* Test unsuccessful entity creation
* Test updating entity data
* Test get entity config
* Test validate entity
* Update entity data by entity_id instead of unique_id
* Remove unnecessary uid unique check
* remove schema_options
* test fixture for entity creation
* clean up group address schema
class can be used to add custom serializer later
* Revert: Add light platfrom
* remove unused optional_ga_schema
* Test GASelector
* lint tests
* Review
* group entities before adding
* fix / ignore mypy
* always has_entity_name
* Entity name: check for empty string when no device
* use constants instead of strings in schema
* Fix mypy errors for voluptuous schemas
---------
Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
* Report non-awaited/non-locked config entry platform forwards
Its currently possible for config entries to be reloaded while their platforms
are being forwarded if platform forwards are not awaited or done after the
config entry is setup since the lock will not be held in this case.
In https://developers.home-assistant.io/blog/2022/07/08/config_entry_forwards
we advised to await platform forwards to ensure this does not happen, however
for sleeping devices and late discovered devices, platform forwards may happen
later.
If config platform forwards are happening during setup, they should be awaited
If config entry platform forwards are not happening during setup, instead
async_late_forward_entry_setups should be used which will hold the lock to
prevent the config entry from being unloaded while its platforms are being
setup
* Report non-awaited/non-locked config entry platform forwards
Its currently possible for config entries to be reloaded while their platforms
are being forwarded if platform forwards are not awaited or done after the
config entry is setup since the lock will not be held in this case.
In https://developers.home-assistant.io/blog/2022/07/08/config_entry_forwards
we advised to await platform forwards to ensure this does not happen, however
for sleeping devices and late discovered devices, platform forwards may happen
later.
If config platform forwards are happening during setup, they should be awaited
If config entry platform forwards are not happening during setup, instead
async_late_forward_entry_setups should be used which will hold the lock to
prevent the config entry from being unloaded while its platforms are being
setup
* run with error on to find them
* cert_exp, hold lock
* cert_exp, hold lock
* shelly async_late_forward_entry_setups
* compact
* compact
* found another
* patch up mobileapp
* patch up hue tests
* patch up smartthings
* fix mqtt
* fix esphome
* zwave_js
* mqtt
* rework
* fixes
* fix mocking
* fix mocking
* do not call async_forward_entry_setup directly
* docstrings
* docstrings
* docstrings
* add comments
* doc strings
* fixed all in core, turn off strict
* coverage
* coverage
* missing
* coverage
