Piston Help - Need someone to tell me what I have wrong

#1

1) Give a description of the problem
light still turning off after motion clears despite switch change

2) What is the expected behaviour?
Garage light turns on with motion or door open, off after motion clears except when switch is activated

3) What is happening/not happening?
light turns on/off by motion but activating switch does not prevent light from turning off after motion clears

4) Post a Green Snapshot of the pistonimage
(UPLOAD YOUR IMAGE HERE)

image
image.png1178×905 43.2 KB

split this topic #2

A post was split to a new topic: Need this one proofed

#3

First, turn on TRACE and post a full log for us.

This is not a solution to your question. I’m just confused about your sensors.

Line 23 : Any of Switch 19 or Switch 21 changes to ON

Are those virtual switches or devices?
If they are devices, shouldn’t it be Motion_Sensor changes to ACTIVE and Door_Sensor changes to OPEN?

EDIT…
I guess it could be up to how the DH was coded. Maybe ACTIVE=ON, INACTIVE=OFF and OPEN=ON, CLOSED=OFF.

#4

I moved the second piston to a separate topic, to reduce the confusion.

#5

I do not see any reference to motion sensors in this piston…

… but in regards to the switches, your piston above looks decent, as long as you do not use Switch 19 to turn it off. (line 35)

For troubleshooting, here are the steps for Trace and Logging that I recommend.

#6

They are a virtual contact sensor and virtual motion sensor.

image
image.png1178×905 47.2 KB

9/14/2020, 7:24:55 AM +271ms
+1ms ╔Received event [TeBa’s House].test = 1600093495268 with a delay of 3ms
+62ms ║RunTime Analysis CS > 18ms > PS > 5ms > PE > 39ms > CE
+65ms ║Runtime (40168 bytes) successfully initialized in 5ms (v0.3.110.20191009) (62ms)
+69ms ║╔Execution stage started
+85ms ║║Condition #9 evaluated false (11ms)
+87ms ║║Condition group #3 evaluated false (state did not change) (13ms)
+97ms ║║Condition #21 evaluated false (7ms)
+99ms ║║Condition group #15 evaluated false (state did not change) (8ms)
+110ms ║║Condition #28 evaluated false (8ms)
+111ms ║║Condition group #25 evaluated false (state did not change) (9ms)
+114ms ║╚Execution stage complete. (45ms)
+116ms ╚Event processed successfully (116ms)

#7

The TEST button will not run your piston. You will have to walk in front of your motion sensor or open the door to get the piston to trigger properly and produce a log that we can digest.

#8

Do you walk into a room and flick the switch within about ten seconds when you want the light to stay on? If so what happens if you wait for say fifteen seconds?

I ask because I can see the potential for a semaphore wait delaying a motion or contact event by ten seconds. A log would likely be diagnostic.