1 min read
It is now possible to use translation placeholders for (custom) service actions.
The service action example now shows how to supply the available description placeholders during the registration of the service action.
Move URLs from service descriptions and translation strings into description placeholders.
It's now possible to provide static values to be used in an entity translation using placeholders.
Action translations defined in strings.json are no longer included in responses from the WebSocket get_services command and the REST /api/services endpoint because they were incomplete and the Home Assistant frontend did not use them.
It's now possible to provide translations for device names, including support for static values to be used as placeholders.
Service call descriptions have been changed to support filtering. It's possible to add a filter to a service call to not show entities which do not support the service call, it's also possible to add a filter to a service call field to not show fields which are not supported by a selected entity to the user.
