Me too! I split my stuff into separate pistons because I thought the longer pistons could be the cause of the missed triggers. Weird enough, similar triggers and actions created using the SharpTools rule engine do work and do not miss any trigger…but there I needed to create 3 different rules: open, close and stay open.
I really don’t know. The very same piston structure sometimes works, sometimes doe not. When I see the logs, I simply don’t see the events on a subscribed device. It opens or closes and there is nothing in the log…
IF Something triggers
Then Turn off Switch 3
IF Switch 3 changes to off
Then do stuff
I avoid this logic because whenever “Something triggers”, it executes a command, that is also a trigger… Thereby starting the piston all over at the top, and going thru the code line by line once again.
No issues there. I do have some stuff running there for testing purposes. Did not give up on WC just yet t:) However, rules in Sharptools are much more limited than in WC, but definitely more flexible vs the native automation capabilities available via the ST apps.
I guess its “possible” that triggers that worked 100% of the time for over a year (like in my case) could simply stop working 100% of the time due to a change in infrastructure between smartthings and Webcore and our inefficient/poorly written code.
But I think the more likely case is, something happened recently at either smartthings or Webcore that is now causing our code to not function 100% like it used to. There are several of these threads out there written slightly different across smartthings and webcore.
I’ve also been experiencing similar issues with lights not always turning on or off based on motion. Also noticing much more delay and inaccuracy with door sensors. Webcore telling me a door was left opened although the door is closed and logged as such in smartthings.
Definitely something going on but I haven’t looked into it much though.
For everybody who has found this thread recently and may not have read the whole thing, I’m convinced the root cause is a SmartThings issue. They acknowledged as much on this thread:
From the investigation I’ve done on my own, I’m fairly certain that this issue is also the root cause of what @WCmore observed:
Which means that the platform issue has been around for a while and nobody noticed it because it didn’t happen as often as it does now.
Technical details: each webcore piston is a child smartapp on the platform. Therefore, if a piston misses an event, that really means that a smartapp missed an event. It also means that this issue isn’t specific to webcore – it should affect anything running on the SmartThings platform. In fact, people on the linked thread have seen the same issue with other smartapps and even the native automation.
I had quite a few dark rooms last night, but went to bed instead of troubleshooting. It seemed fine this morning. To me, I thought I was having internet/connectivity issues as nobody else posted comments about trouble.
Is it working for you today? If not, I might start up my testing pistons to see if events are disappearing.
Resolved - All services have fully recovered and users will no longer see issues with device control, creating locations in the new SmartThings app, or loading the SmartThings Classic app and web interface. Please contact us via support.smartthings.com if you have any questions.
Jan 13, 23:49 EST
Update - Users may also experience issues creating locations in the new SmartThings app, as well as issues loading the SmartThings Classic app and web interface. We continue to investigate.
Jan 13, 23:27 EST
Investigating - Some users in the Americas may be experiencing issues with delays or intermittent failures in device control from the mobile app and automations. We are currently investigating and will provide updates as available.
Jan 13, 21:30 EST