webCoRE piston delay

Since daylight savings time I’ve been having problems with my pistons not firing at the correct time. Sometimes it’s 30 minutes after it was suppose to run. Sometimes 5 minutes.

This morning it was suppose to run at 6:50:00 but it executed at 6:50:30. Since it was 30 seconds after the time it was suppose to run, the piston failed to execute because of wrong time.

Anyone know how to fix this?

you need to pause all your time based pistons then resume them again, for some reason daylight saving has screwed everyones pistons.

you might have been better posting this in the WebCoRE Community, you are more likely to get a quicker response to WebCoRE related issues there.

A number of webCoRE users have been reporting issues with timer based pistons for the last couple of weeks, not just since DST, though one user recently tentatively suggested that it seemed that the problems may suddenly have lifted. Often the pistons have not been running at all and the recovery procedures have kicked in. I’ve also seen one which had multiple semaphore waits for no apparent reason.

A semaphore wait means the piston has been triggered while it is already running and the new execution has backed off for ten seconds to give the original time to finish. It is perfectly normal (though perhaps not ideal) if multiple triggers can fire round about the same time , or if the piston changes something that will cause it to be triggered again. It is not normal if the piston is only being triggered by a single ‘happens at’ timer.

The semaphore wait happened at 6:50:38 am. The piston seems to have run at 6:50:30 am. It would be interesting to know if it actually triggered late, or if it was completely missed and it was the recovery procedure that ran it.

webCoRE has a recovery procedure that looks out for pistons that failed to execute when scheduled and executes them. Without this the piston’s next run might not get scheduled.

1 Like

This is the exact scenario I was seeing get progressively worse over the last two or so weeks. I have a piston that constantly sets variables based on times of day. It was getting triggered late or missed at an increasing rate - and the cleanup procedure was firing it. I don’t have anything that’s so time sensitive it can’t slide +/- 30 minutes so I didn’t worry about it. Then suddenly a few days ago it got better.

The return to normal (I won’t call it a repair, we dont know what the problem was) seems suspiciously timed alongside the maintenance ST did this weekend for the reported outage. All of my pistons seem to be triggering within a couple milliseconds of the trigger time now…

I may just be lucky or not noticed it, but I have not seen any of these issues, I have many time based pistons.

I am in the UK, not sure if that is making any difference.

I’m pretty sure not only country, but ST shard makes a difference. Your WebCoRE pistons are actually running inside the WebCoRE smartapp which is inside your ST Cloud tenant, the WebCoRE dashboard website is just a user interface. So when your cloud is out of whack, your pistons might be too… If a Shard - say NA04 is acting up. Everyone on NA04 could see the issue while the other North American shards and you guys in the UK won’t know anything happened.

2 Likes

Thanks for the advice! I have paused them all and resumed them. I will see how they all go this evening and in the morning!

© 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.