Another "Piston Does Not Subscribe to Any Events" Issue

#1

1) Give a description of the problem
I have a piston that works for about a week and then it just stops. If I go in and “re-save” the piston, then it will work again for about a week. When I go to look at the piston, it says at the top -

“This piston does not subscribe to any events. Unless executed by other means, it will never run on its own.”

2) What is the expected behavior?
This piston should automatically run every morning at 9:00 am and arm the house alarm to “stay” as long as no one is home. It should also run every night at 1:00 am and arm the house alarm to “stay” as long as everyone is home.

3) What is happening/not happening?
It works for about and week and then stops and gives me the above mentioned error message. I can “resave” the piston and it will work for another week…

4) Post a Green Snapshot of the pistonimage

ss
ss.png1178×855 86.2 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)
I can if necessary

#2

Man I’ve never seen a piston doing that???
I had only one that stopped working but re-writing it once solved everything and working since than over a year now.

The only time i had a “Weird” problem was actually caused by a Device Handler. My STHUB was freezing everynight around 9:00pm LOL that was the time one other piston was using the device handler…

So, did you make any changes to your system in ST IDE before tis started happening???

#3

I would likely structure the piston something like this:

Every day at 9AM                                 <-- Trigger
    IF ALL OF Presence 1, 2 & 3 are not present  <-- Condition
    and
    SHM is Disarmed                              <-- Condition
        Then Do stuff
    END IF
END EVERY

Every day at 1AM                                 <-- Trigger
    IF ALL OF Presence 1, 2 & 3 are present      <-- Condition
    and
    SHM is Disarmed                              <-- Condition
        Then Do stuff
    END IF
END EVERY
#4

I will try to rewrite/restructure the piston as you suggested, but do you have any idea what is causing this behavior? I just want to know so that I do not do it again with future pistons…