* Bump ondilo to 0.5.0 and handle errors retrieving data
* Bump ondilo to 0.5.0 and handle errors retrieving data
* Updated ruff recommendation
* Refactor
* Refactor
* Added exception log and updated call to update data
* Updated test cases to test through state machine
* Updated test cases
* Updated test cases after comments
* REnamed file
---------
Co-authored-by: Joostlek <joostlek@outlook.com>
* Bump google-generativeai to v0.5.2
* Avoid exceptions when Gemini responses are blocked
* pytest --snapshot-update
* set error response
* add test
* ruff
* Switch out aiohttp-isal for aiohttp-fast-zlib to make isal optional
aiohttp-isal does not work on core installs where the system has 32bit userland and a 64bit kernel because we have no way to detect this configuration or handle it.
fixes#116681
* Update homeassistant/components/isal/manifest.json
* Update homeassistant/components/isal/manifest.json
* hassfest
* isal
* fixes
* Apply suggestions from code review
* make sure isal is updated before http
* fix tests
* late import
We only did discovery for the key at setup time. If it
changed, a reloaded of the integration was needed to
update the key. We now update it every time we update
the lock detail.
* Turn on thread safety checks in async_dispatcher_send
We keep seeing issues where async_dispatcher_send is called from
a thread which means we call the callback function on the other
side in the thread as well which usually leads to a crash
* Turn on thread safety checks in async_dispatcher_send
We keep seeing issues where async_dispatcher_send is called from
a thread which means we call the callback function on the other
side in the thread as well which usually leads to a crash
* adjust
* Refactor entity_platform polling to avoid double time fetch
Replace async_track_time_interval with loop.call_later
to avoid the useless time fetch every time the listener
fired since we always throw it away
* fix test
* Improve recorder and worker thread matching in RecorderPool
Previously we would look at the name of the threads. This
was a brittle if because other integrations may name their
thread Recorder or DbWorker. Instead we now use explict thread
ids which ensures there will never be a conflict
* fix
* fixes
* fixes
* Use parametrize in drop connect sensor tests
* Use parametrize in drop connect sensor tests
* Make common helper
* Assert the whole entity state
* fix
---------
Co-authored-by: Jan Bouwhuis <jbouwh@users.noreply.github.com>
Co-authored-by: jbouwh <jan@jbsoft.nl>
* Move Totalconnect coordinator to separate module
* Move Totalconnect coordinator to separate module
* Move Totalconnect coordinator to separate module
* store runtime data inside the config entry
* remove unsued constants
* add test for InvalidDeviceAutomationConfig exception
* assert entry
* add more specific type hint
* Convert sensor recorder tests to use async API
* Fix accidentally renamed test
* Avoid unnecessary calls to async_wait_recording_done
* Avoid auto-commits for every state change
* Make sure recorder patches are set up before hass fixture
G JohanssonandGitHub
Joakim PlateandGitHub
SidandGitHub
Franck NijhofandGitHub
Marc MuellerandGitHub
Erik MontnemeryandGitHub
Mr. BubblesandGitHub
tronikosandGitHub
J. Nick KostonandGitHub
elmuratoandGitHub
MichaelandGitHub
Jan-Philipp BeneckeandGitHub
Guido SchmitzandGitHub