No target set | Home Assistant | Page 1

ionic oxide Apr 19, 2026, 11:10 AM

#

I am getting this error message

#

but I do have targets:

spark flower Apr 21, 2026, 10:54 AM

#

Can you share complete yaml?

ionic oxide Apr 22, 2026, 11:39 AM

#

#

#

alias: Home Switch Automations
description: ""
triggers:
  - domain: mqtt
    device_id: bc1aa8e4fe7562007040119ec686b71a
    type: action
    subtype: single
    trigger: device
    alias: Home Switch - Single
    id: Home Switch - Single
conditions: []
actions:
  - data:
      entity_id: input_select.home_status
      option: "On"
    entity_id: input_select.home_status
    alias: "Home Status: On"
    action: input_select.select_option
mode: restart

spark flower Apr 22, 2026, 1:21 PM

#

Having the entity under data is a bit of an old think. I think it does still work but looks like the GUI has a buggy implementation for it.

Change it to:

alias: Home Switch Automations
description: ""
triggers:
  - domain: mqtt
    device_id: bc1aa8e4fe7562007040119ec686b71a
    type: action
    subtype: single
    trigger: device
    alias: Home Switch - Single
    id: Home Switch - Single
conditions: []
actions:
  - data:
      option: "On"
    target:
      entity_id: input_select.home_status
    alias: "Home Status: On"
    action: input_select.select_option
mode: restart

ebon blaze Apr 22, 2026, 2:55 PM

#

The target is defined twice. Once under data and once on root level of the action

#

That last one is really outdated, it still works, but I haven't seen it in years

#

I guess the main reason for the error is that it's defined two times now

ionic oxide Apr 22, 2026, 8:46 PM

#

Ah! Thanks 🙂

data:
option: "On"
target:
entity_id: input_select.home_status
alias: "Home Status: On"
action: input_select.select_option

worked

#

I've actually noticed it in a fewplaces

#

data: {}
entity_id: climate.mitsubishi_hvac
action: climate.turn_off

entity_id: input_boolean.motion_sensor_status
action: input_boolean.turn_on

#

changed them:

action: input_boolean.turn_on
metadata: {}
target:
entity_id: input_boolean.motion_sensor_status
data: {}

and it works

#

#

I wonder when it will break one day

eternal beacon Apr 23, 2026, 2:57 AM

#

I'm getting those errors for this use case:

spark flower Apr 23, 2026, 1:26 PM

#

@eternal beacon data_template had been deprecated for a long time now...

spark flower Apr 23, 2026, 1:27 PM

#

ionic oxide I wonder when it will break one day

I don't think it's really in the way in the backend so will probably keep working. But I don't think the frontend has any priority to support it when they change things around.

ebon blaze Apr 23, 2026, 6:37 PM

#

eternal beacon I'm getting those errors for this use case:

As addition to the comment of @spark flower , you can just use data instead of data_template
And target also accepts templates

eternal beacon Apr 23, 2026, 9:29 PM

#

Thanks for the feedback
Changing data_template to data gives this in the visual editor, and the [No target set] error still shows

ebon blaze Apr 24, 2026, 6:08 AM

#

You removed the entity_id key

#

And you now put it under data

#

It's either

action: scene.turn_on
target:
  entity_id: scene. whatever

Or

action: scene.turn_on
data:
  entity_id: scene. whatever

#

Not

action: scene.turn_on
data:
  target: scene. whatever

eternal beacon Apr 27, 2026, 6:49 AM

#

OK, I changed the YAML to your second option and that shows as the 2nd screen shot in the GUI:

#

But the [No target set] error still displays:

#

#

Changing the YAML to your first option got rid of the error:

#

#No target set