Bring the target picker everywhere targets are picked

[nielsrowinbik]

Problem statement

The target picker introduced in #2 lets users select entities by area, floor, label, or device, and dynamically resolves the full entity set at runtime. It is not available everywhere users pick targets, however. The entity state trigger is a prominent example: it remains a plain entity selector with none of the flexibility the new picker offers. The same is true of other surfaces like the history and logbook viewers, where users also select entities to scope what they see. Users who have adopted the new picker in automations find the inconsistency jarring, and miss out on its benefits in places where they matter just as much.

Community signals

• This Discord conversation specifically calls out the entity state trigger as a place users want the new target picker.

Scope & Boundaries

In scope

• Extending the target picker to all places in the UI where users currently select entities or targets through a plain entity selector, including but not limited to triggers, conditions, and tools like the history and logbook viewers

Not in scope

• Changes to the target picker's capabilities (covered in other opportunities)
• Wildcard-based targeting

Foreseen solution

An audit of all surfaces using a plain entity selector and replacing them with the target picker in a systematic rollout.

Risks & open questions

1. Are there surfaces where a plain entity selector is intentionally more appropriate than the full target picker? We should audit before assuming a blanket rollout is correct.

Appetite

3 weeks: 1 week for the audit, another 2 weeks for the changes.

Execution issues

No response

Decision log

Date	Decision	Outcome