Setting template variable to persist throughout automation actions

@brahmafear wrote:

I have a need for the following:

Trigger on door opening
Record from camera.
Delay 10s to allow recording.
Send pushbullet notification which includes camera recording.

The issue is that I need the pushbullet action to be templated based on the state of a sensor before the 10s delay. Is there any way to use a template variable to save that sensor’s state, then delay, then access that template variable in a later action? My understanding was that template variables are local to the template they are in.

I can think of a few workarounds involving creating separate scripts that are called by the automation but wanted to ask if there was an easier way to do this.

Posts: 4

Participants: 2

Read full topic