I do something similar myself to track variables that do not change within a certain timeframe. Rather than using the Timers feature (which works just fine, plus it gives you the ability to track how much time is left), I just use one trigger to do both tasks. When the variable changes, it does 2 actions. Action 1 removes all delayed actions for itself. Action 2 performs the actions associated with the variable not changing and is delayed by the time limit for taking the doesn't-change action. So, an example of the process is
- "change_tracking" variable changes value.
- "Change Didn't Happen" trigger executes.
- Action 1 removes any as-yet executed Actions 2 items.
- Action 2 is scheduled (delayed 5 minutes) to send me an email notifying me that the change didn't take place.
- 4 minutes later, "change_tracking" variable changes.
- "Change Didn't Happen" trigger executes.
- Action 1 removes the previously scheduled Action 2 item that would have told me a change didn't take palce.
- Action 2, again, is scheduled (delayed 5 minutes) to send me an email.
- 3 minutes later, "change_tracking" variable changes.
- (and this keeps repeating)
This doesn't allow you to see the last time the variable changed, so if that is important to you, Jay's solution is probably a better one, but it does have the advantage of only requiring the setup of 1 trigger and doesn't require the creation of any new Timer devices.