1) Give a description of the problem
I’ve had a piston that on every weekday at a certain time makes a LIFX light turn on dim and increase in brightness from 0 to 100% over a 15 minute period, and then an hour later it turns the lamp off. That has been working great for nearly a year. The other day it stopped working, even though I can see in the webCORE logs that webCoRE is telling the lights what to do, such as:
Executed physical command [Main Lamp].setLevel([47]) (218ms)
Executed physical command [Main Lamp].setLevel([55]) (204ms)
Skipped execution of physical command [Main Lamp].off([]) because it would make no change to the device. (4ms)
Executed [Main Lamp].off (6ms)
Executed virtual command [Main Lamp].sendNotification (10ms)
Execution stage complete. (41ms)
The only thing I can think of that changed is that a few days ago I updated webCoRE and its 4 components within the SmartThings IDE to the latest version of webCORE. I had been using an older version. I did not make any changes to the piston whatsoever.
2) What is the expected behavior?
Light turns on dim, fades in, turns off later.
3) What is happening/not happening?
Light is not turning on at all. I can use the LIFX app to manually turn the lamp on and off and set its brightness just fine. Also other pistons I have that turn other LIFX lights on and off based on virtual switches are working just fine.
**4) Post a Green Snapshot of the piston!
Image of piston is attached.
5) Attach any logs (From ST IDE and by turning logging level to Full)
4/19/2018, 6:59:59 AM +218ms
+0ms ╔Received event [Home].time = 1524135600000 with a delay of -783ms
+239ms ║RunTime Analysis CS > 30ms > PS > 49ms > PE > 161ms > CE
+242ms ║Runtime (39487 bytes) successfully initialized in 49ms (v0.3.104.20180323) (240ms)
+243ms ║╔Execution stage started
+258ms ║║Cancelling statement #2’s schedules…
+266ms ║║Skipped execution of physical command [Main Lamp].off([]) because it would make no change to the device. (4ms)
+267ms ║║Executed [Main Lamp].off (6ms)
+280ms ║║Executed virtual command [Main Lamp].sendNotification (10ms)
+284ms ║╚Execution stage complete. (41ms)
+286ms ║Setting up scheduled job for Fri, Apr 20 2018 @ 6:10:00 AM EDT (in 83400.497s), with 1 more job pending
+296ms ╚Event processed successfully (296ms)
4/19/2018, 6:19:58 AM +158ms
+1ms ╔Received event [Home].time = 1524133199600 with a delay of -1442ms
+178ms ║RunTime Analysis CS > 25ms > PS > 46ms > PE > 107ms > CE
+181ms ║Runtime (39488 bytes) successfully initialized in 46ms (v0.3.104.20180323) (180ms)
+182ms ║╔Execution stage started
+388ms ║║Executed physical command [Main Lamp].setLevel([100]) (199ms)
+390ms ║║Fast executing schedules, waiting for 1113ms to sync up
+1706ms ║║Executed physical command [Main Lamp].setLevel([100]) (198ms)
+1724ms ║╚Execution stage complete. (1542ms)
+1727ms ║Setting up scheduled job for Thu, Apr 19 2018 @ 7:00:00 AM EDT (in 2400.116s), with 1 more job pending
+1737ms ╚Event processed successfully (1737ms)
4/19/2018, 6:19:52 AM +374ms
+0ms ╔Received event [Home].time = 1524133193539 with a delay of -1166ms
+180ms ║RunTime Analysis CS > 24ms > PS > 44ms > PE > 113ms > CE
+183ms ║Runtime (39488 bytes) successfully initialized in 44ms (v0.3.104.20180323) (182ms)
+184ms ║╔Execution stage started
+433ms ║║Executed physical command [Main Lamp].setLevel([99]) (243ms)
+436ms ║╚Execution stage complete. (251ms)
+438ms ║Setting up scheduled job for Thu, Apr 19 2018 @ 6:19:59 AM EDT (in 6.788s), with 4 more jobs pending
+448ms ╚Event processed successfully (448ms)
The above is a snippet of the logs. Basically log repeats what is listed above every 6 seconds, except for the part at 6:19:58 AM which is supposed to turn the light off.
Also as a test when the light did not come on and did not change in intensity, despite all the log entries showing it is changing the light, I manually put the light on. Then when 6:19:58 AM came around the log showed it sent the Off command to the light, but it stayed on.
Thank you in advance for the help!
