Accept more templates in service fields

[arturpragacz]

Proposed change

The templated initial schema was made to allow templates also on the level of individual keys.

Currently both of the following work correctly:

target: "{{ {'device_id': [var1, var2]} }}"

target:
  device_id:
    - "{{ var1 }}"
    - "{{ var2 }}"

but the following fails:

target:
  device_id: "{{ [var1, var2] }}"

This PR fixes that problem.

Alternative to #149911.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add examples of templated targets home-assistant.io#41586
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (websocket_api) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of websocket_api can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign websocket_api Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
If you are the author of this PR, please leave a comment if you want to keep it open. Also, please rebase your PR onto the latest dev branch to ensure that it's up to date with the latest changes.
Thank you for your contribution!

[Copilot]

Pull Request Overview

This PR adds support for using dynamic templates that evaluate to lists directly in target service fields (area_id, device_id, floor_id, label_id), without requiring a mixed list syntax. Previously, only entity_id supported this pattern where a single template could return a list.

Key Changes

• Extended the _TARGET_SERVICE_FIELDS_TEMPLATED schema to allow dynamic_template as a standalone option for area_id, device_id, floor_id, and label_id fields
• Added test coverage for the new functionality showing templates that evaluate to lists (e.g., "{{ ['area-42', 'area-51'] }}")

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
homeassistant/helpers/config_validation.py	Added dynamic_template as a valid schema option for target service fields (ATTR_DEVICE_ID, ATTR_AREA_ID, ATTR_FLOOR_ID, ATTR_LABEL_ID) to allow templates that return lists
tests/helpers/test_service.py	Added test case verifying that templates evaluating to lists work correctly for all target fields

[emontnemery]

Looks good, but consider improving comments in the tests.
Also, the new functionality should be documented.

[emontnemery]

LGTM, thanks @arturpragacz 👍