1) Give a description of the problem
I am debugging a piston and need to see the attributes associated with a device as they’re saved (specifically, level and switch state). I capture this info to a variable but cannot figure out how look at the actual values. If I text the variable to myself, the value is always “Empty device list.” Is there a way to see what values are being captured?
2) What is the expected behavior?
Lights are off. Piston runs, captures state (which is off), turns lights on waits 2 minutes and then restores state, which should be off. Log shows piston restoring lights to 100%, not 0%. I need view the values the piston is grabbing when it runs.
3) What is happening/not happening?
Device state doesn’t appear to be being restored properly. I want to see what values are being captured so I know what should be restored.
**4) Post a Green Snapshot of the piston![image|45x37]
**5) Attach any logs
I’ve bolded the area in the log where I set the variable. It’s those values that I want to expose and look at.
9/25/2018, 12:44:51 PM +992ms
+0ms ╔Received event [Home].execute = :32cb8712b15ef6863581585ad4206678: with a delay of 135ms
+127ms ║RunTime Analysis CS > 26ms > PS > 58ms > PE > 44ms > CE
+130ms ║Runtime (41610 bytes) successfully initialized in 58ms (v0.3.108.20180906) (129ms)
+131ms ║╔Execution stage started
+138ms ║║Cancelling statement #16’s schedules…
+191ms ║║Executed physical command [null].speak([Motion detected on the patio. Alarm has been activated and all cameras are now recording.]) (46ms)
+192ms ║║Executed [LANnoucer].speak (49ms)
+196ms ║║Cancelling statement #1’s schedules…
+211ms ║║Executed virtual command [Patio Lights].saveStateLocally (7ms)
+216ms ║║Executed virtual command [Patio Lights].setVariable (1ms)
+220ms ║║Executed virtual command [Patio Lights].wait (1ms)
+221ms ║║Waiting for 200ms
+562ms ║║Executed physical command [Patio Lights].setLevel([100]) (135ms)
+563ms ║║Executed [Patio Lights].setLevel (138ms)
+567ms ║║Executed virtual command [Patio Lights].wait (0ms)
+569ms ║║Requesting a wake up for Tue, Sep 25 2018 @ 12:46:52 PM MDT (in 120.0s)
+574ms ║╚Execution stage complete. (443ms)
+576ms ║Setting up scheduled job for Tue, Sep 25 2018 @ 12:46:52 PM MDT (in 119.995s)
+584ms ╚Event processed successfully (584ms)
REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.