Pistons Stopped Working

#1

I noticed that my pistons were not firing when trigger events were occurring so I wrote a very simple piston to test things. I see the trigger events in the ST IDE but it seems my pistons aren’t reacting to events. Any thoughts as to how I can get the house working again are appreciated.

As a note, I am aware of what happened this morning and upgraded to the WC release that was posted a few hours ago. Also:

  • I upgraded to the release that was posted to Github this morning.
  • My PC clock is correct.
  • I’ve opened, edited and saved a number of pistons that aren’t running but that doesn’t help
  • I see the event that should trigger the piston in the ST IDE log
  • I don’t see any errors in the IDE log

Piston I am using for troubleshooting (posting the red version for additional clarity)

piston test
piston test.png1178×589 52.6 KB

From the Piston Log:
11/5/2017, 11:10:47 AM +725ms
+0ms ╔Starting piston… (v0.2.0fb.20171026)
+329ms ║╔Subscribing to devices…
+333ms ║║Subscribing to French Doors.contact…
+426ms ║║Subscribing to Chandelier…
+427ms ║╚Finished subscribing (101ms)
+458ms ╚Piston successfully started (458ms)

From the IDE:
3f18f9ef-6ac4-4649-a46a-88680ff17fb7 11:12:35 AM: debug Parse returned [French Doors was closed, French Doors was closed, French Doors was inactive, French Doors was 61°F, French Doors Battery was 63%, French Doors was -80 dBm, French Doors Signal (LQI) was: 96%]
3f18f9ef-6ac4-4649-a46a-88680ff17fb7 11:12:33 AM: debug Parse returned [French Doors was closed, French Doors was closed]
3f18f9ef-6ac4-4649-a46a-88680ff17fb7 11:12:32 AM: debug Parse returned [French Doors was -80 dBm, French Doors Signal (LQI) was: 95%, French Doors was -10,-1002,-1]
3f18f9ef-6ac4-4649-a46a-88680ff17fb7 11:12:30 AM: debug Parse returned [French Doors was -80 dBm, French Doors Signal (LQI) was: 98%, French Doors was -9,-1002,9]
3f18f9ef-6ac4-4649-a46a-88680ff17fb7 11:12:27 AM: debug Parse returned [French Doors was -79 dBm, French Doors Signal (LQI) was: 98%, French Doors was -6,-1002,5]
3f18f9ef-6ac4-4649-a46a-88680ff17fb7 11:12:24 AM: debug Parse returned [French Doors was opened, French Doors was opened]
3f18f9ef-6ac4-4649-a46a-88680ff17fb7 11:12:24 AM: debug Parse returned [French Doors was active, French Doors was -80 dBm, French Doors Signal (LQI) was: 90%]

Edit: I created a second test piston. It also fails to run:

second simple piston test
second simple piston test.png1178×375 35.8 KB

#2

@ady624. I update Webcore today and pistons are running again, however if you have a timer for 6:00 am it sets the timer to 5:00 scheduled?

#3

Some of my pistons that aren’t working don’t have a timers. I updated WebCOre this morning after reading about the issues people were having. About an hour later a delivery person ran my doorbell but the piston that should have run when the doorbell is run didn’t fire. I looked at other pistons and they weren’t firing either so I wrote two simple test pistons. One should turn off a light when a door opens. It doesn’t work and nothing is written to the WC log. I do see the door open event in the ST IDE. Also, I can use Ask Alexa, Alexa and the ST app to control my devices so this seems specific to WC.

The second test piston should send a push every minute. It doesn’t run either. Here’s the log for that one:

11/5/2017, 12:11:32 PM +397ms
+0ms ╔Starting piston… (v0.2.0fb.20171026)
+153ms ║╔Subscribing to devices…
+251ms ║╚Finished subscribing (100ms)
+273ms ║Setting up scheduled job for Sun, Nov 5 2017 @ 12:12:32 PM MST (in 59.995s)
+415ms ╚Piston successfully started (415ms)

What’s weird is I see it count down, go to pending, and then it starts counting up:

countup
countup.jpg1891×209 35.4 KB

#4

Your logs are saying you are still running 0fb.
Did you check the publish box when you did the updates?

#5

I’m pretty sure I did but I just manually updated everything and it looks like my pistons are running again. Thanks!

#6

Check your scheduled timers

#7

I went out for a few hours and came back to a dead house again. I did the update this morning and all started working fine.
Anyone else having a secondary hiccup?

#8

Yep…

#9

Yep same issue here as well, I have a piston that refresh a device every 30 seconds but nothing happens and the timer just keeps goinf up and up

#10

Please keep posts in one place,

closed #11