* Alarm state from enum
* Fixes
* Set final
* Fix rebase
* Test const
* Fix breaking version
* Fix other for alarm_control_panel
* Fix integrations
* More
* More
* More
* More
* Fix zha
* Replace _attr_state
* Fix alarm_control_panel
* Fix tests
* Fixes
* Mods
* Change some
* More
* More
* More
* Tests
* Last tests
* Return enum
* Fix zha
* Remove not needed check
* Fix wording
* Fix homekit
* Mod prometheus
* Fix mypy
* Fix homekit
* Fix ifttt
* Update sensor.py for new FALMOT Sensors
First Integration attemp to support ValvePosition as Sensor for HmIP-FALMOT-C12
* Update sensor.py
* Update sensor.py
* Add Valve Position to FALMOT-C12
* modified: devcontainer
* Service für minimum vale postion hinzugefügt.
* update to services
* Service call optimized
* Add valvePosition to HomematicIP Cloud for Falmot-C12 and show only channels that are connected with an motorized actuator
* Fix some tests
* Add icon for service
* Fix tests, add check for ValveState in icon
* Remove minimum valve service
* REmove minimum valve
* Use list comprehension for devices, support other terminal blocks
* Remove unused constant
* Check correct channel
---------
Co-authored-by: thecem <46648579+thecem@users.noreply.github.com>
* [homematicip_cloud] Add service to set cooling mode
* Create seperate test for cooling
* Rename service to set_home_cooling_mode
* Raise exception when accesspoint not found
* 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
* Default names for visible profiles
* Increase number of devices in test
* remove unnecessary check
* Add testcase and split another into two
* Add type annotations and docstring
* Remove code which not belongs to the PR
* Add myself to codeowners
Co-authored-by: Sid <27780930+autinerd@users.noreply.github.com>
Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
Co-authored-by: J. Nick Koston <nick@koston.org>
* Migrate homematicip_cloud to use async_forward_entry_setups
Replaces deprecated async_setup_platforms with async_forward_entry_setups
* adapt test, this test should be rewritten