* Not valid hvac modes now fails
* Fix some tests
* Some more
* More
* fix ruff
* HVAC
* Fritzbox
* Clean up
* Use dict[key]
---------
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Use setup_test_component_platform in Climate tests
* Rename mock integration helper
* Change name to register_test_integration
* Change name in tests
* Fix ruff format
* Climate temperature out of range
* Fix test sensibo
* use temp converting for min/max
* Fix
* Fix mqtt tests
* Fix honeywell tests
* Fix Balboa tests
* Fix whirlpool test
* Fix teslemetry test
* Fix plugwise test
* Fix tplink test
* Fix generic thermostat test
* Fix modbus test
* Fix fritzbox tests
* Honewell
* Check exposure in climate intent
* Check exposure in todo list
* Check exposure for weather
* Check exposure in humidity intents
* Add extra checks to weather tests
* Add more checks to todo intent test
* Move climate intents to async_match_targets
* Update test_intent.py
* Update test_intent.py
* Remove patch
* 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
Erik MontnemeryandGitHub
Paul BotteinandGitHub
Abílio CostaandGitHub
MichaelandGitHub
Norbert RittelandGitHub
Matthias AlphartandGitHub
epenetandGitHub
Michael HansenandGitHub
Jan BouwhuisandGitHub
Marc MuellerandGitHub
Brent PetitandGitHub
J. Nick KostonandGitHub