* Fix projector timeout in pyprojector lib v1.0.10
* Fix projector timeout by increasing time between power command and refresh.
* Bump jvcprojector lib to ensure unknown power states are handled
* 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
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>
It turns out we have custom components that are writing to the area registry using the async APIs from threads. We now catch it at the point async_fire is called. Instead we should check sooner and use async_fire_internal so we catch the unsafe operation before it can corrupt the registry.
It turns out we have custom components that are writing to the device registry using the async APIs from threads. We now catch it at the point async_fire is called. Instead we should check sooner and use async_fire_internal so we catch the unsafe operation before it can corrupt the registry.
* Move thread safety check in entity_registry sooner
It turns out we have a lot of custom components that are writing
to the entity registry using the async APIs from threads. We now
catch it at the point async_fire is called. Instread we should check
sooner and use async_fire_internal so we catch the unsafe operation
before it can corrupt the registry.
* coverage
* Apply suggestions from code review
Robert Resch
Steve Easley
Mr. Bubbles
dontinelli
Paulus Schoutsen
J. Nick Koston
Shay Levy
Joost Lekkerkerker
Jan Bouwhuis
hopkins-tk
Martin Hjelmare
Marco van 't Wout
Raman Gupta
Paul Bottein
Aidan Timson
Erik Montnemery
Brett Adams
Luke Lashley
On Freund
Michael Hansen