Piston timer counting backwards - up instead of down

#1

1) Give a description of the problem
I have several pistons that have been running for years. These are basic on at X time and off at Y time… As of 8/16/2020, these pistons are no longer firing and when I view them in webcore, their timers are counting up vs. counting down until the next on/off event. Of about 10 similar pistons, about 7 of them have this issue and the other 3 seem to be fine. I’ve tried to edit/re-save the pistons that have the issue. Once saved, the piston begins counting down correctly again. However, at some point the issue reappears as when I check them again several hours later, they are counting up again… Was there a recent update that might be causing this? Any idea on how to resolve?

#2

I’ve seen this sometimes. I think it may be congestion/resource shortfall somewhere in the whole system. The counting up seems to indicate the event has occurred, but the piston has not been activated yet.

Recently I’ve been seeing issues with 2 lights turning on. Both fire at dusk by one piston, but there can be a delay of upto 15 secs between the 2 turning on. They used to turn on together. I suspect the delay is caused as the second lights DH runs in the cloud (fibaro dimmer) This doesn’t happen all the time, but first started a few weeks ago.

#3

Thanks. I migrated from the classic ST app to the new ST app a few days prior to noticing this. Any idea if this could this have something to do with it?? Also, I agree that the upward counter is probably starting at the time the piston should have fired… Just can’t understand why the pistons aren’t firing… They all show a “last executed date” of 8/16/2020…

#4

I’ve not migrated yet, but have had both apps installed since I started using smartthings a few years ago. At the moment I seem able to use both apps and seem to have everything available in most. However I use webcore for everything, I just have a couple of routines driving 2 virtual switches from my fibaro double switch as the fibaro isn’t fully usable from webcore. Maybe there have been some changes to facilitate the use of the new app which are causing issues.

I’ve been waiting for some advice/others experience of migrating before I clicked the button.