Run device tracker device registry updates immediately
without the call_soon delay. This listener does not
need a delay and it only adds overhead in this case.
* Defer creating tasks we know are going to wait on the entity platform semaphore
When looking at whats going on with aiomonitor-ng, I noticed
we end up creating a lot of tasks that block waiting for the
executor because of the entity platform parallel_updates semaphore.
When we know the tasks are going to block we now await them
in sequence to avoid feeding the loop a herd of tasks that
will block on the semaphore
* change during iteration fix
* change during iteration fix
* cleanup
* cleanup
* fix vizio test
* Improve performance when serializing small bits of JSON
Making json_bytes a partial reduced the run time to
build the small JSON messages by ~18.75%
We serialize a lot of small messages over the websocket
* typing
* Use httpx instead of requests for mjpeg camera images that need digest
Avoids jump to executor
* Use httpx instead of requests for mjpeg camera images that need digest
Avoids jump to executor
* stream as well
* fix
* fix
* Switch some frequently called call_laters to call_at
call_at is a bit faster than call_later since call_later
is a wrapper around call_at.
We call at lot of these at startup so it helps a bit when
we are resource constrained
* update test
* update test
* Complete migration of persistent notifications
Persistent notifications are no longer stored in
the state machine and no longer fire events
* Complete migration of persistent notifications
Persistent notifications are no longer stored in
the state machine and no longer fire events
* fixes
* fixes
* fixes
* ws test
* update tests
* update tests
* fix more tests
* fix more tests
* more fixes
* fix
* fix person
* fix person
* keep whitelist
* use singleton
* Add additional coverage to history websocket api
related issue #93258
* Add additional coverage to history websocket api
related issue #93258
* Fix results when union query ends up at the end instead of front
* Apply suggestions from code review
* resort
* zero instead
* fix exception
* fix tests
* Fix not retrying on connection reset during nexia config entry setup
fixes
```
2023-05-26 00:15:39.129 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Alexander for nexia
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 558, in _request
resp = await req.send(conn)
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 670, in send
await writer.write_headers(status_line, self.headers)
File "/usr/local/lib/python3.11/site-packages/aiohttp/http_writer.py", line 130, in write_headers
self._write(buf)
File "/usr/local/lib/python3.11/site-packages/aiohttp/http_writer.py", line 75, in _write
raise ConnectionResetError("Cannot write to closing transport")
ConnectionResetError: Cannot write to closing transport
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/nexia/__init__.py", line 47, in async_setup_entry
await nexia_home.login()
File "/usr/local/lib/python3.11/site-packages/nexia/home.py", line 385, in login
request = await self.post_url(self.API_MOBILE_ACCOUNTS_SIGN_IN_URL, payload)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/nexia/home.py", line 157, in post_url
response: aiohttp.ClientResponse = await self.session.post(
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 572, in _request
raise ClientOSError(*exc.args) from exc
aiohttp.client_exceptions.ClientOSError: Cannot write to closing transport
```
* coverage
* Significantly speed up recorder event listener
This code is called every time an event happens since it
subscribes to all events. Its our most frequently called
listener out of the box.
It used to have a seperate filter function but it was
later combined after core had some previous refactoring.
It was never optimized after that happened.
This change reduces the run time by ~70%
* decruft
* Move constant values to separate file
* Move constant values to separate file
* Add config flow to lastfm
* Add tests
* Add config flow to lastfm
* Add tests
* Add tests
* Add tests
* Add extra form for main user and autofill with friends
* Add extra form for main user and autofill with friends
* Add extra form for main user and autofill with friends
* Add extra form for main user and autofill with friends
* Add OptionsFlow
* Add tests
* Fix feedback
* Fix feedback
* Fix feedback
* Fix feedback
* Fix test
* Apply suggestions from code review
Co-authored-by: G Johansson <goran.johansson@shiftit.se>
* Update config_flow.py
* Update config_flow.py
* Update config_flow.py
* Update homeassistant/components/lastfm/config_flow.py
Co-authored-by: G Johansson <goran.johansson@shiftit.se>
* Add tests
* Cleanup
* Update config_flow.py
* Update config_flow.py
* Update config_flow.py
* Fix test
* Fix feedback
* Codeowner lastfm
* Fix feedback
* Fix feedback
* Parametrize errors
* Parametrize errors
* Parametrize errors
* Finish tests
---------
Co-authored-by: G Johansson <goran.johansson@shiftit.se>
pycsspeechtts uses the requests library, but Microsoft TTS previously
caught HTTPException from the standard library. This is changed to
catch requests.HTTPError and return `(None, None)` consistent with
other TTS integrations. This will properly raise HomeAssistantError
for display in the frontend.
Follow up to PR #92215 which adds tests for Microsoft TTS.
* Update Microsoft TTS supported languages
`script.microsoft_tts` scrapes Microsoft Azure documentation for
the list of supported languages and saves them to
`homeassistant.generated.microsoft_tts` for use in the component.
This adds support for more TTS languages, like fa-ir (Persian).
* Improve xpath query for Microsoft TTS languages
* Remove asserts for Microsoft TTS languages
* Add more tests for Microsoft TTS languages
* Fix arest switch to set output when connection is lost
Signed-off-by: disaster37 <linuxworkgroup@hotmail.com>
* fix: lint
Signed-off-by: disaster37 <linuxworkgroup@hotmail.com>
---------
Signed-off-by: disaster37 <linuxworkgroup@hotmail.com>
* Refactor zwave_js.cover and improve test coverage
* Remove extra fixtures
* cleanup old stuff
* Get coverage to 100
* Remove redundant stuff
* Revert all changes to tests
* Update conftest.py
* airzone: climate: fix max/min temps
The library now provides AZD_ABS_TEMP_MAX/AZD_ABS_TEMP_MIN which are useful for
devices with different max/min temperatures depending on the current working
mode (HEAT vs COOL).
These new values will have the highest/lowest max/min of both modes.
Until now, the max/min of the current working mode (HEAT/COOL) would be set
when starting Home Assistant, limiting the temperature range if the device
mode was changed after that.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* airzone: climate: update max/min temps
Some devices have different max/min climate temps depending on the active
mode (HEAT vs COOL), so we should update these values.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* Revert "airzone: climate: update max/min temps"
This reverts commit 988194d486.
* Revert "Revert "airzone: climate: update max/min temps""
This reverts commit e4ead24f71.
* tests: airzone: add max/min climate changes test
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* tests: airzone: fix dict copy
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
---------
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* add sensors to roborock
* add value_fn typing
* fixed strings
* Update homeassistant/components/roborock/sensor.py
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
* change to work time instead of time left
* added time left back
* fixed tests
* made diagnostic
---------
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
* Prevent firmware update error when internet blocked
* fix styling
* switch back to async_config_entry_first_refresh
* fix still raising when starting
* missing return
* Catch CancelledError
* Add proper support for zwave_js Indicator CC
* remove stale test
* Make all indicators diagnostic
* only set entity category if it is specified
* Only set properties from discovery if specified
* Conditionally set assumed state as well
* fix const name
* Don't create task
* Disable property keys 3-5 by default
* add additional dispatcher_connects so we catch all signals
* be consistent about order
* rename new discovery parameter
* comment
* exclude property keys 3-5
* fix remove logic
* add comment so I don't forget
* Switch entity category to config where necessary
* cut line
* less lines
* Update homeassistant/components/zwave_js/switch.py
Co-authored-by: kpine <keith.pine@gmail.com>
* Move async_remove to respond to interview started event
* Set up listener immediately so we don't wait for platform creation
* remove dupe import
* black
* append
---------
Co-authored-by: kpine <keith.pine@gmail.com>
* Do optimistic state update for Z-Wave multilevel switch entities
* simplify
* define constant for setting value to previous value
* Rework to only consider value of 255 and only places where we know that the previous state is known by the integration due to the service being called
* missed commit
* better code
* Add tests and use constant from lib
* fix logic
* fix bug
* Add comments with more details
* Update event when coordinator updates data.
* Move function to make diff easier to view
* Actually make it easier to view
* Move all tasks calculation to extra_state_attributes.
* Fix directv attribute media_position_updated_at
Fix to update media_position_updated_at attribute when media_position attribute is updated.
* Do not update media_position_updated_at when paused
* Add a DataUpdateCoordinator to Hydrawise
* Replace DATA_HYDRAWISE with DOMAIN
* Replace persistent notification with a ConfigEntryNotReady exception
* Changes requested during PR review
* Add a type annotation to the `monitored_conditions` field.
Co-authored-by: epenet <6771947+epenet@users.noreply.github.com>
---------
Co-authored-by: epenet <6771947+epenet@users.noreply.github.com>
* Truncate long URLs
URL's longer than 256 characters will result in a
`homeassistant.exceptions.InvalidStateError`. This fixes that problem
and adds 2 extra_state_attributes: `full_url`, and `truncated`.
Fixes#89249
* Refactor to use function ref in entity description
* Add new preset to Tado to enable geofencing mode
Add new 'auto' preset mode to enable Tado to be set to auto geofencing
mode. The existing ‘home’ and ‘away’ presets switched Tado into manual
geofencing mode and there was no way to restore it to auto mode.
Note 1: Since preset modes (home, away and auto) apply to the Tado home
holistically, irrespective of the Tado climate entity used to select
the preset, three new sensors have been added to display the state of
the Tado home
Note 2: Auto mode is only supported if the Auto Assist skill is enabled
in the owner's Tado home. Various checks have been added to ensure the
Tado supports auto geofencing and if it is not supported, the preset is
not listed in the preset modes available
* Update codeowners in manifest.json
* Update main codeowners file for Tado component
* Get hostname id from get_settings
* Add try except in get_hostname_id function
* Update tests after adding get_hostname_id function
* Revert "Update tests after adding get_hostname_id function"
This reverts commit 5fa4e533cb.
* Add test for G2 models in config flow.
* Add test for helper module.
* Fix test for numbers.
* Revert "Add try except in get_hostname_id function"
This reverts commit 059f5bd9b4.
* Update variable name with known hostname ids to be private
---------
Co-authored-by: Stefan Gmeiner <stefangm42@gmail.com>
* airzone: climate: add Temperature range support
This is useful for HEAT_COOL climate mode (Airzone AUTO).
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* trigger CI
---------
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* Refactor zwave_js.sensor and add test coverage
* use walrus
* inherit config parameter class from list class
* use walrus in more places
* improve config parameter test
* Add change service
* test subtract
* Test no change if timer not running
* Modify example
* Raise
* Finalize
* test event
* Fix tests
* Fix tracking time
* Added new integration to support Electra Smart (HVAC)
* fixes + option to set scan interval
* renamed the module to electrasmart and added unittests
* added non tested files to .coveragerc
* changed the usage from UpdateCoordinator to each entity updates it self
* small fixes
* increased pypi package version, increased polling timeout to 60 seconds, improved error handling
* PARALLEL_UPDATE=1 to prevent multi access to the API
* code improvements
* aligned with the new HA APIs
* fixes
* fixes
* more
* fixes
* more
* more
* handled re-atuh flow
* fixed test
* removed hvac action
* added shabat mode
* tests: 100% coverage
* ran hassfest
* Update homeassistant/components/electrasmart/manifest.json
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* Update homeassistant/components/electrasmart/manifest.json
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* Update homeassistant/components/electrasmart/manifest.json
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* Update homeassistant/components/electrasmart/climate.py
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* address Shay's comments
* address Shay's comments
* address more comments
---------
Co-authored-by: Shay Levy <levyshay1@gmail.com>
* init commit
* use official version release
* remove options
* moved first refresh to gather
* add extra tests
* remove model_sepcification
* remove old mqtt test
* bump to 13.4
* fix dndtimer
* bump to 14.1
* add status back
* bump to 17.0
* remove error as it is not used
* addressing mr comments
* making enum access use get()
* add check for empty hass data
The default behavior of these warnings is to go to stderr, which in
some setups goes easily unnoticed. For example in Docker based ones,
they end up only in the container logs, and not e.g. in the HA log.
Capture these to make them available in logs where other such messages
are, and to make them subject to filtering as usual.
https://docs.python.org/3/library/logging.html#logging.captureWarnings
* Add always connected option to Yale Access Bluetooth
If the lock does not support push updates via advertisements or you want lock operation to be more responsive, you can enable always connected mode. Always connected will cause the lock to stay connected to Home Assistant via Bluetooth, which will use more battery.
* Update homeassistant/components/yalexs_ble/config_flow.py
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
---------
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Update UpCloud config entry data on successful reconfig
* Add already configured test
* Improve success case request mocking
So that the data fetch that might happen in the background after success
won't trash the test log with misleading errors.
* Simplify already configured test
Thanks-to: Martin Hjelmare <marhje52@gmail.com>
* remove impossible test
IndividualAddress telegrams are not processed by xknx.telegram_queue
* Use Telegrams helper class for group monitor messages
* Store 50 telegrams in deque for group monitor
* Send recent telegrams at once on connection of group monitor
* Update KNX-frontend to support group monitor prepopulation
* Copy openai_conversation to google_generative_ai_conversation
This is to improve diff of the next commit with the actual implementation.
Commands used:
cp -r homeassistant/components/openai_conversation/ homeassistant/components/google_generative_ai_conversation/
cp -r tests/components/openai_conversation/ tests/components/google_generative_ai_conversation/
find homeassistant/components/google_generative_ai_conversation/ tests/components/google_generative_ai_conversation/ -type f | xargs sed -i \
-e 's@openai_conversation@google_generative_ai_conversation@g' \
-e 's@OpenAI Conversation@Google Generative AI Conversation@g' \
-e 's@balloob@tronikos@g'
* Add google_generative_ai_conversation to Google brand
* Google Generative AI Conversation
* Sync recent openai changes
* handle empty responses
* Remove as_compressed_state cache
All calls to as_compressed_state are now covered by a higher level
JSON cache so there is no need to store these in memory anymore
* Remove as_compressed_state cache
All calls to as_compressed_state are now covered by a higher level
JSON cache so there is no need to store these in memory anymore
* Disconnect rather than just logout at end of config flow
Neither the connection or the requests session will be reused, so
there's no reason just to logout. Do all of the connection closure
so we get all of huawei-lte-api's cleanups explicitly done.
* Name connect functions consistently, analoguous to disconnect
* telegram device trigger initial
* add Telegrams helper class
to parse and convert Telegram only once instead of once per device trigger
* translation
* label for extra_field
* test device trigger
* test trigger callback removal
* rename extra_field key to same name as used in trigger
* typo
* Fix onvif cameras that cannot parse relative time
The spec requires that the camera can parse relative or absolute timestamps
However there are many cameras that cannot parse time correctly.
Much of the event code has been offloaded to the library and
support to determine if the camera has broken time and switch
to absolute timestamps is now built into the library
* adjust verison
* fixes
* bump
* bump
* bump
* more fixes
* preen
* fix resume
* one more fix
* fix race in webhook setup
* bump to 3.1.3 which has more fixes for broken camera firmwares
* bump 3.1.4 for more fixes
* fix
* fix comment
* bump
* fix url limit
* bump
* more fixes
* old hik uses -s
In #90191 we use the same ssl context for httpx now to avoid
a memory leak, but httpx previously allowed sslv2/sslv3 for
unverified connections
This reverts to the behavior before #90191
* Disable cleanup_closed for aiohttp.TCPConnector with cpython 3.11.2+
There is currently a relatively fast memory leak when using
cpython 3.11.2+ and cleanup_closed with aiohttp
For my production instance it was leaking ~450MiB per day
of `MemoryBIO`, `SSLProtocol`, `SSLObject`, `_SSLProtocolTransport`
`memoryview`, and `managedbuffer` objects
see https://github.com/aio-libs/aiohttp/issues/7252
see https://github.com/python/cpython/pull/98540
* Update homeassistant/helpers/aiohttp_client.py
Joost Lekkerkerker
J. Nick Koston
Álvaro Fernández Rojas
Aaron Godfrey
Artem Draft
Raj Laud
Erik Montnemery
Paul Frank
Bram Kragten
G Johansson
Franck Nijhof
Justin Vanderhooft
Maciej Bieniek
starkillerOG
Dominik
Philip Peitsch
badewanne1234
IceBotYT
Dara Adib
RenierM26
Jan Bouwhuis
disaster37
Matrix
Marc Mueller
Marcel van der Veldt
Michał Modzelewski
Raman Gupta
Luke
epenet
Martin Malina
Vova-SH
MarkGodwin
rappenze
ad0p
Jeff Grieger
David Knowles
Colin Robbins
Tom Schneider
Mike Heath
Mike Degatano
Jafar Atili
Guido Schmitz
ollo69
jjlawren
Jesse Hills
uvjustin
Chris Talkington
Ludy
luar123
Tom
Brett Adams
Patrick Li
andarotajo
Michael Mraka
chiefdragon
Aaron Bach
Tom Harris
rikroe
erikbadman
Diogo Gomes
Matthias Alphart
Dmitry Vlasov
Steven Looman
Ernst Klamer
henryptung
Mick Vleeshouwer
Tom Brien
Jan Čermák
Ville Skyttä
Andre Lengwenus
Joakim Plate
MatthewFlamm
Michael Benz
Nerdix
Ziv
tronikos
Pascal Vizeli
Daniel Gangl
Jens Østergaard Nielsen
Stephan Uhle
Pieter Viljoen
imerla1
puddly
Justas