'Bypass' State Confusion

Other Devices & Integrations Door Locks & Sensors
1

So…

I have a motion detector that is the crux of a series of scenes tied via triggers. However, my assumption (which is either wrong or something else is broken) was that if the motion detector was in ‘Bypass’ it wouldn’t kick off a trigger that is looking for that state. I initially thought that my trigger was wrong. However, both states for a motion detector:

  1. A sensor (door/window/motion/etc) is tripped.
  2. An armed sensor is tripped. <— I thought this would make the difference

…do the exact same thing. The scene just starts a ‘Countdown Timer’ device and other scenes are based on the state of that. So… What good is the ‘Bypass’ if the trigger doesn’t obey the state of it? Or is it just me?

Thanks in advance!

UPDATE:
OK, so after reboot now it works as expected. If the detector is in ‘Bypass’ the trigger does not get tripped. However, if I have it in ‘Bypass’ and then switch to ‘Arm’ the trigger will trip - regardless of whether or not there’s motion, just on the initial setting of the state - after that it works fine. Is this to be expected?

2

I’m not sure if my Foscam camera motion sensors function the exact same way as your sensor, but from my use with them I’ve found that when I initially check the camera on my iPhone app it actually triggers the motion sensor. When I arm the camera motion sensors for scenes it doesn’t seem to trip them initially, but it may be that your particular sensor does in fact trip when it is initially set to ‘arm’.

3

@windexh8er,

Welcome!

IIUC, your motion sensor is not showing the ‘red running guy’, it is in Bypass, and then when you switch to Arm, your scene triggers as if the sensor was tripped, and it is still showing the ‘green standing guy’?