Pistons stopped working correctly

#1

1) Give a description of the problem
Piston was working fine last week. This week, having some weird log and things doesn’t work

3) What is happening/not happening?
My camera motion stopped being detected by webcore.
Had to change the piston to time base trigger instead of motion
When I unlock my door, received some time/recovery log

5) Attach logs after turning logging level to Full

+0ms ╔Received event [Maison].time/recovery = 1607513217112 with a delay of 0ms
+135ms ║RunTime Analysis CS > 20ms > PS > 57ms > PE > 57ms > CE
+137ms ║Runtime (39920 bytes) successfully initialized in 57ms (v0.3.110.20191009) (136ms)
+138ms ║╔Execution stage started
+139ms ║╚Execution stage complete. (1ms)
+140ms ╚Event processed successfully (140ms)

I don’t know what changed since last week, any ideas ?

thanks!

#2

BTW my Camera is an Arlo

When I check in the event on smartthings for that device I see that no motion event has been sent since 2 days

Pretty sure webcore is base on those events to work ?

What can be done?

#3

Looks like others are experiencing issues with Arlo the past few days including motion detection.

#4

oh god, will look at it, thanks!

#5

That is a recovery event. There are two sources of these which present slightly differently and I never remember which is which. However the bottom line is that every piston you run checks to see if any other pistons have scheduled events that are overdue by more than thirty seconds, and there is also a regular timed check at longer intervals for the same thing (you’ll find this in the webCoRE settings in the app). Any such pistons are sent a ‘recovery’ event so they are able to run and set up future schedules (pistons schedule their own next run).

So it looks like a timer event has got lost. It isn’t something you should see routinely unless something is broken in ST.