mirror of
https://github.com/home-assistant/developers.home-assistant.git
synced 2025-04-19 10:57:14 +00:00
f5f51fa125
* Clarify blog post about entity service action schema changes * Update blog/2024-08-27-entity-service-schema-validation.md Co-authored-by: Martin Hjelmare <marhje52@gmail.com> --------- Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
1.3 KiB
1.3 KiB
| author | authorURL | title |
|---|---|---|
| Erik Montnemery | https://github.com/emontnemery | Validation of entity action schemas |
Registering entity service actions allows integration authors to pass in:
- No schema (
None) - A dictionary, which will be converted to a voluptuous schema by passing it to
cv.make_entity_service_schema - A custom voluptuous schema
For the third case, a warning will now be logged when registering an entity action with a custom schema which does not meet at least one of these criteria:
- A validator returned by
cv.make_entity_service_schema - A validator returned by
cv.make_entity_service_schema, wrapped in avol.Schema - A validator returned by
cv.make_entity_service_schema, wrapped in avol.All
In Home Assistant Core 2025.10, it will no longer be possible to register an entity action with a custom schema not meeting this requirement.
The reason for the change is that if cv.make_entity_service_schema is not used, the service will not automatically support all possible ways of targeting entities.
More details can be found in the developer documentation and in core PRs #124102 and #125057.