Hi @Sir_Goodenough, The example I’ve given is a simplified automation. My real automation is complex, I have numerous options that are still being developed, rearranged etc. I’d like to know which option generated the message.
The trigger object contains information about your automation’s State Trigger.
trigger.entity_id will contain the entity_id of whichever entity was responsible for triggering the State Trigger (useful if there is more than one entity listed in the State Trigger).
trigger.to_state.state will contain the entity’s new state. For example, on or off.
He’s trying to know which choose path was taken from this. data or somewhere…
Pretty sure not a thing without creating a variable that’s updated based on path taken…
To my knowledge, there’s no accessible index value for the options of a choose statement. So you can’t self-referentially determine that the thirdchoose option was selected.
In any case, there should be no need for a so-called choose.option given that you can hard code the index value directly in the option. It’s unclear why the OP needs this capability (i.e. this seems to be an XY problem).