Pistons have stopped working! [daylight savings time issues]

fixed
#1

Hello,

I left everything working this night. I mean the wall switches with webCoRE pistons. Now (in this morning) all the switches programmed with pistons do not work anymore. I verified:

  • all is published and updated
  • no one has access but me
  • if I manage the light within the SmartThings they are working
  • I am using pistons from about 3 months. Never stop working until now!

Do U know what is happening?

WebCoRE pistons stopped working
Piston stopped running
Issue with daylight savings possibly?
All Pistons stopped working today
How can I record the state of a group of devices?
Pistons Stopped Working
Motion Light Piston Stopped Working Last Night
#2

I think something is going on. Other people are reporting issues.

#3

Yeah, nothing working here either. Updated to latest release.

#4

This is major. Affects the homes of the people directly.

Did this happening before in the history of the (web)CoRE? Please vote to find out the gravity of the situation:

  • It happened before (to me or someone I know).
  • Did not happened before.

0 voters

Show results
#5

I just moved some of my piston from CoRE to WebCore, time to go back…

#6

I don’t think the CoRE is working, neither in this moment. I think this affects both the CoRE and the webCoRE.
Who is using CoRE, please confirm.

#7

I’m still have CoRe piston and they are running fine

#8

That is interesting.

I thought until now that is the same thing/server under the hood…

#9

Same here, nothing working this morning, lots of logs last night repeating after 2:00am

#10

all pistons not triggering here either on the graph-eu01-euwest1.api.smartthings.com shard…

#11

I was started a poll to find out how big it is… Please vote if it happened to you before, or not.

https://community.webcore.co/t/pistons-stop-to-work/2159/4?u=daniionescubrasov

#12

All pistons stopped working at 2:30AM ET
Problem seems isolated to webCore because devices can still be controlled and are properly reporting.

#13

Same here. I’ve tried a bunch of things to recover, no luck.

1 - Edit / Save Piston
2 - Pause / Resume Piston
3 - Disable / Enable all pistons in app in ST app
4 - Rebuilding my cache in the webCoRE ST app

Also, nothing showing up in the logs. WebUI seems to be fine. As others have said, normal ST operations are working via the ST app / Amazon Echo.

#14

@webCoRE_Minions
@ady624

#15

Maybe we should help @ady624 to write a piston which will alert him if the system goes down. :stuck_out_tongue_winking_eye:

#16

This does bring up a point. If @ady is unavailable, are there other minions able to step in? This is a must if this is to be a long term home automation solution.

#17

Just sent him a text and woke him up lol… He’s taking a look

#18

Morning guys, any errors in (IDE) logs? Just woke up :wink:

#19

There doesn’t seem to be any log activity at all.

#20

Just these…

7:23:11 AM: warn Piston OfficeFan was sent a recovery signal because it was 8591430ms late
7:23:11 AM: warn Piston OCCUPANCY|Master Bedroom was sent a recovery signal because it was 19915518ms late
7:23:11 AM: warn Piston EVENT|Arm at Night was sent a recovery signal because it was 6791419ms late
7:23:11 AM: warn Piston EVENT|Vacation was sent a recovery signal because it was 22326942ms late