1) Give a description of the problem
I created a small piston that writes energy usage data to a thingspeak account. It works great and have been using it for a few weeks now.
I decided to make a small update. I added a second data write for energy cost. This piston runs every hour at 30 past the hour. I have seen this same failure behavior in a another piston that runs at the same time every day. I basically tried to do the same thing. I moved to this piston since it runs more often so I could watch what was happening.
2) What is the expected behaviour?
I just added a 15 second wait after the first HTTP Get because with my thingspeak account you can only write data every 15 seconds. So I assumed it would wait 15 seconds and then complete the piston
3) What is happening/not happening?
What happens is the piston starts running every 15 seconds. I assume the wait is changing the run every time. Is this expected behavior? If so, is there a way I can put in a delay or do I need to use 2 separate timers?
**4) Post a Green Snapshot of the piston!
5) Attach logs after turning logging level to Full
By the time I caught what was happening it had written a lot of data to the log and I get get back to the point it started.
Just before posting this I did one last search and found this post. So I guess using a a wait is not going to work. I see a few ways to get around this but I thought I would ask what others might do.