-
-
Notifications
You must be signed in to change notification settings - Fork 34.5k
Description
The problem
Describe the issue you are experiencing
When using a blueprint target selector and selecting an entity (for example, from WLED, Shelly, or any entity tied to a device), the automation will work as expected.
However, once saved, if you go to the device page of that entity (e.g., WLED or Shelly) and check the Automations section, the linked automation will not appear.
This seems to happen only when the blueprint uses the target selector. If the blueprint uses an entity selector instead, the automation will show up under the device’s Automations tab.
Describe the behavior you expected
Automations created using a blueprint target selector should be shown under the associated device’s Automations tab.
Steps to reproduce the issue
Steps to Reproduce
- Use the Sensor Light blueprint (which uses a target selector).
- Select a light entity linked to a device and save the automation.
- Go to Settings > Devices & Services > [Device containing the light entity].
- Scroll to the Automations section.
Actual Result:
The automation is not shown under the device, even though it uses one of its entities.
To Verify It's Due to the target Selector
- Use a blueprint that utilizes an entity selector, such as Manual Control Status Tracker .
- Select the same light entity used in the previous step and save the automation.
- Go to the same device page under Devices & Services.
Expected Result:
This time, the automation does appear in the Automations section of the device.
What version of Home Assistant Core has the issue?
2025.5.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response