* fix
* Fix
* Fix
* Update homeassistant/helpers/config_validation.py
Co-authored-by: Erik Montnemery <erik@montnemery.com>
* Fix
* Fix
* Fix
* Fix
* Add more tests
* Fix
* Fix tests
* Add tests
* Let's see what the CI does
* It fails on the code that tested the thing ofc
* It fails on the code that tested the thing ofc
* Revert test thingy
* Now the test works again, lovely
* Another one
* Fix websocket thingy
* Only copy when needed
* Improve comment
* Remove test
* Fix docstring
* I think this now also work since this transforms trigger to platform
* Add comment
* Update homeassistant/helpers/config_validation.py
Co-authored-by: Erik Montnemery <erik@montnemery.com>
* Update homeassistant/helpers/config_validation.py
Co-authored-by: Erik Montnemery <erik@montnemery.com>
* Update homeassistant/helpers/config_validation.py
Co-authored-by: Erik Montnemery <erik@montnemery.com>
* Check for mapping
* Add test
* Update homeassistant/helpers/config_validation.py
Co-authored-by: Erik Montnemery <erik@montnemery.com>
* Update test to also test for trigger keys
---------
Co-authored-by: Erik Montnemery <erik@montnemery.com>
* Reinitialize zeroconf discovery flow on unignore
* Adjust tests
* Improve comments
* Fix logic for updating discovery keys
* Add tests
* Use mock_config_flow helper in new config_entries test
* Add discovery_keys attribute to ConfigEntry
* Update zeroconf rediscovery
* Change type of ConfigEntry.discovery_keys
* Update tests
* Fix DiscoveryKey.from_json_dict and add tests
* Fix test
---------
Co-authored-by: J. Nick Koston <nick@koston.org>
* Add a syntax for merging lists of triggers
* Updating to the new syntax
* Update homeassistant/helpers/config_validation.py
Co-authored-by: Erik Montnemery <erik@montnemery.com>
* fix suggestion
* update test and add comments
* not actually json
* move test to new file
* update tests
---------
Co-authored-by: Erik Montnemery <erik@montnemery.com>
* Don't raise when registering entity service with invalid schema
* Update homeassistant/helpers/service.py
Co-authored-by: Robert Resch <robert@resch.dev>
---------
Co-authored-by: Robert Resch <robert@resch.dev>
* Limit maximum template render output to 256KiB
fixes#124931
256KiB is likely to still block the event loop for an unreasonable amont of
time but its likely someone is using the template engine for large
blocks of data so we want a limit which still allows that but has
a reasonable safety to prevent the system from crashing down
* Update homeassistant/helpers/template.py
* Do a sanity check of schema passed to EntityPlatform.async_register_entity_service
* Only attempt to check schema of Schema
* Handle All/Any wrapped in schema
* Clarify comment
* Apply suggestions from code review
Co-authored-by: Robert Resch <robert@resch.dev>
---------
Co-authored-by: Robert Resch <robert@resch.dev>
* Limit intent / llm API device_class slots to only necessary services and limited set of values
* Fix ruff errors
* Run ruff format
* Fix typing and improve output schema
* Fix schema and improve flattening
* Revert conftest
* Revert recorder
* Fix ruff format errors
* Update using latest version of voluptuous
* Remigrate device_registry created_at/modified_at
Nightly current does not boot up because the device registry
will have KeyError: created_at if the previous nightly was
installed.
* reduce
* split migration per discord comments
* Indicate database migration in /api/core/state response
* Change API response according to review comment
* Adjust API response
* Update test
* Add test
* init
* Update homeassistant/helpers/update_coordinator.py
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
* fix typo, ruff
* consistency with rest, test
* pylint suppression
* ruff
* ruff
* switch to one test
* add last exc
* add tests for auth & Entry Errors
* move exceptions to correct test
* Update update_coordinator.py
Co-authored-by: G Johansson <goran.johansson@shiftit.se>
* test setup call
* simplify
---------
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
Co-authored-by: G Johansson <goran.johansson@shiftit.se>
* Update voluptuous to 0.15.1
* Fix typing issues
* Add type ignores for json result type
* Update voluptuous to 0.15.2
---------
Co-authored-by: J. Nick Koston <nick@koston.org>
* Add script llm tool
* Add tests
* More tests
* more test
* more test
* Add area and floor resolving
* coverage
* coverage
* fix ColorTempSelector
* fix mypy
* fix mypy
* add script reload test
* Cache script tool parameters
* Make custom_serializer a part of api
---------
Co-authored-by: Michael Hansen <mike@rhasspy.org>
* Add expandable support for data entry form flows
* Update config_validation.py
* optional options
* Adjust
* Correct translations of data within sections
* Update homeassistant/components/kitchen_sink/config_flow.py
Co-authored-by: Robert Resch <robert@resch.dev>
* Add missing import
* Update tests/components/kitchen_sink/test_config_flow.py
Co-authored-by: Robert Resch <robert@resch.dev>
* Format code
* Match frontend when serializing
* Move section class to data_entry_flow
* Correct serializing
* Fix import in kitchen_sink
* Move and update test
---------
Co-authored-by: Bram Kragten <mail@bramkragten.nl>
Co-authored-by: Robert Resch <robert@resch.dev>
* Include speech_slots in IntentResponse.as_dict
* Populate speech_slots only if available
* fix typo
* Add test
* test all fields
* Fix another test
---------
Co-authored-by: Paulus Schoutsen <balloob@gmail.com>
* Check exposure in climate intent
* Check exposure in todo list
* Check exposure for weather
* Check exposure in humidity intents
* Add extra checks to weather tests
* Add more checks to todo intent test
* Move climate intents to async_match_targets
* Update test_intent.py
* Update test_intent.py
* Remove patch
* Always do thread safety check when writing state
Refactor the 3 most common places where the thread safety check
for the event loop to be inline to make the check fast enough
that we can keep it long term. While code review catches most
of the thread safety issues in core, some of them still make
it through, and new ones keep getting added. Its not possible
to catch them all with manual code review, so its worth the
tiny overhead to check each time.
Previously the check was limited to custom components
because they were the most common source of thread
safety issues.
* Always do thread safety check when writing state
Refactor the 3 most common places where the thread safety check
for the event loop to be inline to make the check fast enough
that we can keep it long term. While code review catches most
of the thread safety issues in core, some of them still make
it through, and new ones keep getting added. Its not possible
to catch them all with manual code review, so its worth the
tiny overhead to check each time.
Previously the check was limited to custom components
because they were the most common source of thread
safety issues.
* async_fire is more common than expected with ccs
* fix mock
* fix hass mocking
* Automatically fill in slots from LLM context
* Add tests
* Apply suggestions from code review
Co-authored-by: Allen Porter <allen@thebends.org>
---------
Co-authored-by: Allen Porter <allen@thebends.org>