Not sure this would work either on further reflection, If the energy value changes then it starts the timer. If it changes again, does that change the state of the original condition? It’s still TRUE isn’t it, I guess I just need to try it.
Maybe I should just go back to my smartapp for this particular function. The smartapp basically ran a Runin groovy command timer every time there was a energy event. So each energy event would reset the timer. The app did other things as well, that I moved out of the smartapp because they kept not firing. The app had worked great for over a year then all of a sudden timers would just not go off. It was supposed to write daily, weekly, and monthly energy usage to a thingspeak account.
At first it was only the monthly reset that just stop working. I had a cron timer that should write my monthly usage and reset my HEM at the end of my power company’s billing cycle.
I would check and the timer was active and set to fire on the correct date at midnight, but the next morning it would not have fired and I had to manually get my data. After a few months of this I wrote a backup piston in webcore that would check the HEM a couple of minutes after it was supposed to reset and if it wasn’t it would reset it. The webcore piston worked every time. Then after a month or two my hourly writes just stopped. I had made no changes to the smartappp so I got fed up and decided to just move everything to webcore. I did all this about 3 months ago and it has never missed an event.
Anyway if I could set an on event that would restart every time there was an event like the Runin command it would be the best option.