Piston Runs Sometimes

[twodaend]

I have a really simple piston that sets the location to Day and turns off the HSM. However, this piston does not seem to always run. I brought this piston over from SmartThing WebCore and it is doing the same thing now as it previously did. I have no idea why it runs just fine something and not other times.

Here is the log from this morning and it did not run.

1/13/2023, 7:10:00 AM +26ms
+9ms ╔Received event [Home Hub].time = 1673615400000 with a delay of 26ms, canQueue: true, calledMyself: false
+78ms ║RunTime initialize > 77 LockT > 0ms > r9T > 67ms > pistonT > 66ms (first state access 3 m:10 10 67)
+81ms ║Runtime (8402 bytes) initialized in 67ms (v0.3.114.20230103_HE)
+87ms ║╔Execution stage started
+90ms ║║Piston execution aborted due to restrictions in effect; updating piston states
+105ms ║║nullRequesting every schedule wake up at Mon, Jan 16 2023 @ 7:10:00 AM CST (in 259199870ms) for 2 (st:-1)
+106ms ║║Piston Every timer execution aborted due to restrictions in effect
+107ms ║║Exiting piston at end of Every timer block
+111ms ║╚Execution stage complete. (25ms)
+157ms ║Setting up scheduled job for Mon, Jan 16 2023 @ 7:10:00 AM CST (in 259199858ms)
+159ms ╚Event processed successfully (151ms)

[nh.schottfam]

See:

Using Restrictions in webCoRE

In webCoRE restrictions are conditions that can be applied to either the entire piston, or to a statement within the piston. As they only include condition comparisons, they do not cause the piston to execute (there is no automatic subscription to condition comparisons in restrictions) Note, you do not need to use the 'restrictions' syntax in webCoRE, your own if statements can handle restrictions you want. In the IDE, restrictions may not be initially visible: [Screen Shot 2022-02-1…

and

Device events vs. timer events in webCoRE

Pistons run due to events that the piston has subscribed to. Most commonly these events are devices like switches, or sensors that report updated status as changes occur to the device. Another reason a piston can run is a timer. In this case the piston asked to be woken up in the future with a time event. The event happened because the piston requested the event to happen in the future. The subtle but important point here is device events occur because the device had a state change - th…

hint - the restriction is messing you up, code it into the every block vs. have the every block nested underneath it