Timing of storage into a variable

[Allan_P]

@josh, I have several Leviton outlets. I get the $context.event.deviceName and store it to a variable named $CottageOutlet, and its status $context.event.value goes into a variable called $CottageOutletStatus. I have a rule that triggers if an outlet goes offline. Does each time the rule executes have its own instance of the variables? This post would seem to indicate otherwise.

Are variables 'static'?

Internally we refer to variables as Global Variables as they are shared across the system including rules and dashboards. So yes, changes from rule A will be visible in rule B. Can you share more details about what you’re trying to accomplish? One ‘gotcha’ with this is when using a variable as both a trigger and top-level condition within the same rule. In that case, make sure to use Context Variables ($context.event.value), as it’s possible for the event to trigger the rule before the variabl…

The reason I ask is I was wondering whether a variable would get overwritten by a second triggering of the rule within 100’s of milliseconds of the first triggering?

Thanks.

[josh]

The variables are global as the other post indicates.

And yes, the last write into the variable wins even if it’s only a few hundred milliseconds later.