Rules and Expressions with Open Weather API

[josh]

@JKB121

The second time triggers your rule while the first is still running. That will add another instance every time the variable is flipped.

With the updates trigger, that’s absolutely right. The state stays trigger helps deduplicate the events which is why it’s the first thing listed in the unofficial recommendations linked above.

Here’s my response from Ken’s other thread:

@josh

Typical event driven rules won’t run into this problem. This is only an issue when the rule acts upon the variable/device which triggered that rule itself, causing it to loop – and specifically in a way where parallel loop executions could occur.

Example: a rule that triggers when a variable changes to true, then the rule toggles the variable to false, waits, then toggles it true again.

If the variable is set to true, that would start the ‘loop’ running. Then if you manually set the variable to true again, that would start another instance of the ‘loop’ running in parallel.

Make sure to check out the guidance I shared in my reply to your other post. In particular, using state stays as the trigger is a critical step here as it will effectively ‘deduplicate’ those parallel events.