* Upgrade pytest-aiohttp
* Make sure executors, tasks and timers are closed
Some test will trigger warnings on garbage collect, these warnings
spills over into next test.
Some test trigger tasks that raise errors on shutdown, these spill
over into next test.
This is to mimic older pytest-aiohttp and it's behaviour on test
cleanup.
Discussions on similar changes for pytest-aiohttp are here:
https://github.com/pytest-dev/pytest-asyncio/pull/309
* Replace loop with event_loop
* Make sure time is frozen for tests
* Make sure the ConditionType is not async
/home-assistant/homeassistant/helpers/template.py:2082: RuntimeWarning: coroutine 'AsyncMockMixin._execute_mock_call' was never awaited
def wrapper(*args, **kwargs):
Enable tracemalloc to get traceback where the object was allocated.
See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.
* Increase litejet press tests with a factor 10
The times are simulated anyway, and we can't stop the normal
event from occuring.
* Use async handlers for aiohttp
tests/components/motioneye/test_camera.py::test_get_still_image_from_camera
tests/components/motioneye/test_camera.py::test_get_still_image_from_camera
tests/components/motioneye/test_camera.py::test_get_stream_from_camera
tests/components/motioneye/test_camera.py::test_get_stream_from_camera
tests/components/motioneye/test_camera.py::test_camera_option_stream_url_template
tests/components/motioneye/test_camera.py::test_camera_option_stream_url_template
/Users/joakim/src/hass/home-assistant/venv/lib/python3.9/site-packages/aiohttp/web_urldispatcher.py:189: DeprecationWarning: Bare functions are deprecated, use async ones
warnings.warn(
* Switch to freezegun in modbus tests
The tests allowed clock to tick in between steps
* Make sure skybell object are fully mocked
Old tests would trigger attempts to post to could services:
```
DEBUG:aioskybell:HTTP post https://cloud.myskybell.com/api/v3/login/ Request with headers: {'content-type': 'application/json', 'accept': '*/*', 'x-skybell-app-id': 'd2b542c7-a7e4-4e1e-b77d-2b76911c7c46', 'x-skybell-client-id': '1f36a3c0-6dee-4997-a6db-4e1c67338e57'}
```
* Fix sorting that broke after rebase
* Fix loss of ability to control white channel in HomeKit on RGB&W lights
- Fix white channel missing from RGB/W lights
- Fix temp missing from RGB/CW lights
- Fixes#65529
* cover the missing case
* bright fix
* force brightness notify on color mode change as well
* Ensure selected entity is pre-selected in homekit options flow
- We recently adjusted the flow to exclude entities that had
been deleted from breaking the UI validation. We need to include
single entities in the set of all supported entities since
accessory mode has no domain filter
* tweak
* Additional fixes
* small tweak to speed up building the set
* merged fixed version for test branch
* Add turned on or off device trigger to toggle entity
* Renamed changed_states trigger to toggled
* Adjust tests
* Fix homekit triggers test
* Add tests
* Adjust tests after rebase
Co-authored-by: J. Nick Koston <nick@koston.org>
* Convert persistent notification tests to async
* Create/dismiss persistent notifications in exposed functions, not service calls
* Fix notify persistent_notification
* Remove setting up persistent_notification
* Drop more setups
* Empty methods
* Undeprecate sync methods because too big task
* Fix setup clearing notifications
* Fix a bunch of tests
* Fix more tests
* Uno mas
* Test persistent notification events
* Clean up stale comment
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Avoid creating sockets in homekit port available tests
* prevent new bridge from being setup -- its too fast now that the executor job is gone and it revealed an unpatched setup
* Convert all HomeKit service info to string prior to checking for max length
* Added check for None software version
* Added test case for numeric version number
* Update tests/components/homekit/test_accessories.py
Co-authored-by: J. Nick Koston <nick@koston.org>
* Fix style & none version test
* Fix test
* revert other change since it should be covered by the format_sw_version fix
Co-authored-by: J. Nick Koston <nick@koston.org>
- Sometimes homekit will go unresponsive because a pairing for a specific
device is missing. To avoid deleting the config entry and recreating
it, which can be a painful process if there are many bridged entities,
the homekit.unpair service allows forceful removal of the pairings so
the accessory can be paired again.
J. Nick Koston
Joakim Plate
Stackie Jia
Erik Montnemery
epenet
Artem Draft
Sarabveer Singh
Franck Nijhof
Paulus Schoutsen
Lester Lo
Li-Huai (Allan) Lin
Lorenzo Brescanzin
Ville Skyttä
Dave T
Greg Thornton
ha0y
Niccolo Zapponi
Milan Meulemans