Pistons failing on Location Mode change?

Over the last 2 weeks all my Good xxx have been either executing, executing only 50% of the piston or not running at all no matter how many times I tell it to execute. Good Bye, I’m Back and Good night seem to be the worse now. All the other pistons work fine but it appears that anything with “Location” mode change is affected.
These pistons were solid for 2 years and now all this random execution; if at all.
Any suggestions would be appreciated.

Logs show partial execution or the snippet below…

I seem to get a lot of this which I’m not sure what it indicates:
18/09/2019, 18:26:06 +879ms
+1ms +Received event [Home V2].time/recovery = 1568856366872 with a delay of 5ms
+2162ms ¦RunTime Analysis CS > 1989ms > PS > 95ms > PE > 80ms > CE
+2166ms ¦Runtime (50094 bytes) successfully initialized in 95ms (v0.3.10f.20190822) (2161ms)
+2167ms ¦+Execution stage started
+2169ms ¦+Execution stage complete. (1ms)
+2179ms +Event processed successfully (2180ms)
18/09/2019, 18:25:55 +131ms
+0ms +Received event [Home V2].time/recovery = 1568856355127 with a delay of 3ms
+156ms ¦RunTime Analysis CS > 31ms > PS > 65ms > PE > 60ms > CE
+159ms ¦Runtime (50091 bytes) successfully initialized in 65ms (v0.3.10f.20190822) (157ms)
+160ms ¦+Execution stage started
+161ms ¦+Execution stage complete. (1ms)
+162ms +Event processed successfully (163ms)

It started around the time they released firmware version 27.9. They fixed it last week but it appears the issue has resurfaced. There are two threads - one on the ST forum and one on the webCoRE forum where users started reporting problems have returned.


Thanks for the link. I wasn’t sure if I should post here or the WebCore forum.
I’ll keep a watchfull eye on the firmware investigation.

I posted this on the “other side” today in resonse to someone thinking I might have traffic congestion :slight_smile:

I have very little traffic, most of the 25Meg is free all the time; no kids at home anymore :slight_smile: This is the first time in 4 years I have had this message.
Today I still have pistons failing but it’s always on a piston with Location mode.
It almost looks like it does whatever percentage of work in the piston until it encounters the Location change then it dies and the rest of the commands go unexcuted.

I don’t think it’s traffic as I have two devices that seem to be the only ones getting affected. Wait, correction, 1 device and location.

© 2019 SmartThings, Inc. All Rights Reserved. Terms of Use | Privacy Policy

SmartThings; SmartApps®; Physical Graph; Hello, Home; and Hello, Smart Home are all trademarks of the SmartThings, Inc.