* bump fyta_cli to 0.4.0
* Update PLANT_STATUS and add PLANT_MEASUREMENT_STATUS
* bump fyta_cli to v0.4.0
* minor adjustments of states to API documentation
* Add service to log all the current asyncio Tasks to the profiler
I have been helping users look for a task leaks, and need a
way to examine tasks at run time as trying to get someone to
run Home Assistant and attach aiomonitor is too difficult in
many cases.
* cover
If the integration page is accessed right before shutdown it
can trigger the usb scan debouncer which was not marked as
background so shutdown would wait for the scan to finish
* Add thread safety checks to async_create_task
Calling async_create_task from a thread almost always results in an
fast crash. Since most internals are using async_create_background_task
or other task APIs, and this is the one integrations seem to get wrong
the most, add a thread safety check here
* Add thread safety checks to async_create_task
Calling async_create_task from a thread almost always results in an
fast crash. Since most internals are using async_create_background_task
or other task APIs, and this is the one integrations seem to get wrong
the most, add a thread safety check here
* missed one
* Update homeassistant/core.py
* fix mocks
* one more internal
* more places where internal can be used
* more places where internal can be used
* more places where internal can be used
* internal one more place since this is high volume and was already eager_start
* Add matter during onboarding
* test_zeroconf_not_onboarded_running
* test_zeroconf_not_onboarded_installed
* test_zeroconf_not_onboarded_not_installed
* test_zeroconf_discovery_not_onboarded_not_supervisor
* Clean up
* Add udp address
* Test zeroconf udp info too
* test_addon_installed_failures_zeroconf
* test_addon_running_failures_zeroconf
* test_addon_not_installed_failures_zeroconf
* Clean up stale changes
* Set unique id for discovery step
* Fix tests for background flow
* Fix flow running in background
* Test already discovered zeroconf
* Mock unload entry
* Update dependency growattServer for improved error details
Updating to latest version. Since version 1.3.1 it will raise requests.exceptions.HTTPError for unexpected API responses such as HTTP 405 (rate limiting/firewall)
* Improve error details by raising ConfigEntryAuthFailed
Previous code was returning None which the caller couldn't handle
* Use a more appropiate exception type
* Update homeassistant/components/growatt_server/sensor.py
* Update homeassistant/components/growatt_server/sensor.py
* Fix
---------
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
If the integration page is accessed right before shutdown it
can trigger the usb scan debouncer which was not marked as
background so shutdown would wait for the scan to finish
* Small cleanups to climate entity feature compat
Fix some duplicate property fetches, avoid generating a new
enum every time supported_features was fetched if there was
no modifier
* param
* param
* refactor habitica sensors, add strings and icon translations
* Change sensor names
* remove max_health as it is a fixed value
* remove SENSOR_TYPES
* removed wrong sensor
* Move Data coordinator to separate module
* add coordinator.py to coveragerc
* add deprecation warning for task sensors
* remove unused imports and logger
* Revert "add deprecation warning for task sensors"
This reverts commit 9e58053f3b.
* Update homeassistant/components/habitica/strings.json
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
* Update homeassistant/components/habitica/strings.json
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
* Revert "Move Data coordinator to separate module"
This reverts commit f5c8c3c886.
* Revert "add coordinator.py to coveragerc"
This reverts commit 8ae07a4786.
* rename Mana max. to Max. mana
* deprecation for yaml import
* move SensorType definition before TASK_TYPES
* Revert "deprecation for yaml import"
This reverts commit 2a1d58ee5f.
---------
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
* Update dependency growattServer for improved error details
Updating to latest version. Since version 1.3.1 it will raise requests.exceptions.HTTPError for unexpected API responses such as HTTP 405 (rate limiting/firewall)
* Improve error details by raising ConfigEntryAuthFailed
Previous code was returning None which the caller couldn't handle
* Use a more appropiate exception type
* Update homeassistant/components/growatt_server/sensor.py
* Update homeassistant/components/growatt_server/sensor.py
* Fix
---------
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
* Add matter during onboarding
* test_zeroconf_not_onboarded_running
* test_zeroconf_not_onboarded_installed
* test_zeroconf_not_onboarded_not_installed
* test_zeroconf_discovery_not_onboarded_not_supervisor
* Clean up
* Add udp address
* Test zeroconf udp info too
* test_addon_installed_failures_zeroconf
* test_addon_running_failures_zeroconf
* test_addon_not_installed_failures_zeroconf
* Clean up stale changes
* Set unique id for discovery step
* Fix tests for background flow
* Fix flow running in background
* Test already discovered zeroconf
* Mock unload entry
* Add thread safety checks to async_create_task
Calling async_create_task from a thread almost always results in an
fast crash. Since most internals are using async_create_background_task
or other task APIs, and this is the one integrations seem to get wrong
the most, add a thread safety check here
* Add thread safety checks to async_create_task
Calling async_create_task from a thread almost always results in an
fast crash. Since most internals are using async_create_background_task
or other task APIs, and this is the one integrations seem to get wrong
the most, add a thread safety check here
* missed one
* Update homeassistant/core.py
* fix mocks
* one more internal
* more places where internal can be used
* more places where internal can be used
* more places where internal can be used
* internal one more place since this is high volume and was already eager_start
* Avoid creating tasks to update universal media player
Nothing was being awaited in async_update. This entity has polling
disabled and there was no reason to implement manual updates since
the state is always coming from other entities
* manual update
dontinelli