"Execute Routine" stopped working

execution

#1

In the last couple of days my morning and night pistons have not been able to execute a routine (now called automations in the ST App). The logs say that it successfully executed the routine but in looking at the history in the ST App it doesn’t show.

12/16/2020, 6:22:09 AM +493ms
+1ms ╔Received event [Motion Sensor 1].motion = active with a delay of 58ms
+94ms ║Runtime (40209 bytes) successfully initialized in 18ms (v0.3.110.20191009) (92ms)
+95ms ║╔Execution stage started
+236ms ║║Executed virtual command setLocationMode (92ms)
+252ms ║║Executed virtual command executeRoutine (13ms)
+255ms ║╚Execution stage complete. (160ms)
+256ms ╚Event processed successfully (256ms)

Today when I went into the editor the “name” of the routines has changed to a GUID and when I edit to set it back there is no longer a dropdown to select, but instead a text-value field.

Has anyone seen this before?

Here is one of my piston code as well:


#2

Routines were part of the Classic app and ST shut down the Classic app and that part of the platform on Monday. So “execute routine” no longer works.


#3

Ok thanks, this approach was easier than adding every device I wanted to control to WC