#Put an !input zone into a trigger...

1 messages · Page 1 of 1 (latest)

winter grotto
#

I have tried setting it as a trigger variable, and it wouldn't read it. I tried as a straight-up !input, that said this is not string.

Blueprint 'Person Alert Honitor - 2023-02-22' generated invalid automation with inputs .>. Entity ID {{ trigg_1 }} is an invalid entity ID for dictionary value @ data['zone']. Got None
Blueprint 'Person Alert Honitor - 2023-02-22' generated invalid automation with inputs  .>.  value should be a string for dictionary value @ data['zone']. Got None
#
trigger_variables:
  trigg_1: !input zone2monitor
trigger: 
  - platform: zone
    id: enter_trigger
    entity_id: !input people2monitor
    zone: !input zone2monitor
    event: enter
#
trigger_variables:
  trigg_1: !input zone2monitor
trigger: 
  - platform: zone
    id: enter_trigger
    entity_id: !input people2monitor
    zone: '{{ trigg_1 }}'
    event: enter
#

Any Ideas?

#

If I put the text of the actual zone name in there it renders and works...

#

I'm thinking this might be an oversight, as ehtity_id's pull in as !inputs, these should also, right?

winter grotto
rough chasm
#

So I was also looking into how to pass a value of an !input to a field in a trigger. The problem seems to be that support for variables (and templating) is quite limited for triggers.

#

One option could be to use an event trigger, that seems to support templating quite robustly. But you'd need to figure out what event is fired when someone enters the zone...maybe a state change?

winter grotto
#

I get that it would just seem to me one of the few possible uses of a zone selector would be a trigger.... Can't do a lot else with it.