* blebox: udpdate version in manifest and add new sensor key mapping
* blebox: add more sensor types
* blebox: use blebox_uniapi==2.4.1
* blebox: use blebox_uniapi==2.4.2
* blebox: update requirements_all.txt
* blebox: revert introduction of illuminance and power meter sensors set
* Detach name from unique id in incomfort
* Add entity descriptions to incomfort
* Revert "Add entity descriptions to incomfort"
This reverts commit 2b6ccd4c3b.
* Add data coordinator to incomfort integration
* Remove unused code and redundant comment, move entity class
* Use freezer
* Cleanup snapshot
* Use entry.runtime_data
* Use freezer, use mock_config_entry
* Use tick
* Use ConfigEntryError while we do not yet support a re-auth flow, update tests
* Use tick with async_fire_time_changed
* update to new cmd_list type
* Wake battery cams each 1 hour
* fix styling
* fix epoch
* fix timezone
* force full update when using generic update service
* improve comment
* Use time.time() instead of datetime
* fix import order
* 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
* Prelimenary tests for incomfort integration
* Use snapshot_platform
* Use helper
* Ensure the device name is set in device info
* Move snapshot tests to platform test modules
* Move unused snapshot file
* Naming and docstr
* update snapshots
* cleanup snapshots
* Add water heater tests
Michał JaworskiandErik Montnemery
Joost Lekkerkerker
Jan Bouwhuis
Ethem Cem ÖzkanandG Johansson
epenet
Erwin Douna
dependabot[bot]
Diogo Gomes
Paulus Schoutsen
starkillerOG
Franck Nijhof
J. Nick Koston
Jan-Philipp Benecke
Bram Kragten
Stefan Agner
Maciej BieniekandMaciej Bieniek
arturyak
Tsvi Mostovicz
Jack BoswellandJ. Nick Koston
Robert Svensson
Gerben Jongerius
Michał Huryn
ollo69