Reactor not tripping when status is true

ubun2Junky · April 24, 2019, 5:46am

I’ve got a Schlage zwave door lock that I am trying to get reactor to lock when it meets the following conditions.

The door is closed and has been closed for the past 90 seconds.
The door lock is unlocked.

When I check the status and both conditions indicate true the reactor does not trip and the door remains unlocked. When I click on the “trip” button, my door lock will lock as expected. I’m not sure what I’m doing wrong. I’ve attached an image of my setup. Any suggestions are appreciated. Thx.

Conditions
Trip Actions

rigpapa · April 24, 2019, 3:11pm

Please post a Logic Summary here using the link on the Tools page of the ReactorSensor.

ubun2Junky · April 24, 2019, 4:20pm

If you are pasting this report into the Vera forums, please include ALL lines below--please do not edit/omit/redact!

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
   Version: 2.5 config 206 pluginDevice 127
    System: Vera Sercomm G450 firmware 1.7.4001; Lua 5.1
Local time: 2019-04-24T10:16:17-0600, DST=1
House mode: tracking on; current mode 2
  Sun data: 
  Geofence: not running
====================================================================================================================================
Front Door AutoLock (#128)
    Version 19012.1555873326 04/21/19 13:02:06
    Message/status: Not tripped
    Group #1: grpc0x7v6v; false as of 04-18.18:42:23 <grpc0x7v6v>
        =T (service) Front Door Sensor (37) urn:micasaverde-com:serviceId:SecuritySensor1/Tripped = 0 [true/true as of 08:10:27/08:10:27; 1 => 0 at 08:10:27] <condc0x7v6w>
        =f (service) Front Door Lock (58) urn:micasaverde-com:serviceId:DoorLock1/Status = 0 for ge 90s after condc0x7v6w [false/false as of 10:15:16/04-18.18:42:23; 0 => 1 at 10:15:16] <condc0xphex>
    Trip Actions
        Device 58 (Front Door Lock) action urn:micasaverde-com:serviceId:DoorLock1/SetTarget( newTargetValue=1 )
    Untrip Actions (none)
    Events
        04/23/19 19:21:18 condchange: newState=true, cond=condc0x7v6w, oldState=false
        04/23/19 19:21:18 evalchange: newState=true, cond=condc0x7v6w, oldState=false
        04/23/19 19:45:09 devicewatch: device=37, old="0", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="1"
        04/23/19 19:45:10 condchange: newState=false, cond=condc0x7v6w, oldState=true
        04/23/19 19:45:10 evalchange: newState=false, cond=condc0x7v6w, oldState=true
        04/23/19 19:47:50 devicewatch: device=37, old="1", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="0"
        04/23/19 19:47:51 condchange: newState=true, cond=condc0x7v6w, oldState=false
        04/23/19 19:47:51 evalchange: newState=true, cond=condc0x7v6w, oldState=false
        04/23/19 19:58:40 devicewatch: device=37, old="0", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="1"
        04/23/19 19:58:41 condchange: newState=false, cond=condc0x7v6w, oldState=true
        04/23/19 19:58:41 evalchange: newState=false, cond=condc0x7v6w, oldState=true
        04/23/19 19:58:48 devicewatch: device=37, old="1", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="0"
        04/23/19 19:58:49 condchange: newState=true, cond=condc0x7v6w, oldState=false
        04/23/19 19:58:49 evalchange: newState=true, cond=condc0x7v6w, oldState=false
        04/23/19 20:04:02 devicewatch: device=37, old="0", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="1"
        04/23/19 20:04:03 condchange: newState=false, cond=condc0x7v6w, oldState=true
        04/23/19 20:04:03 evalchange: newState=false, cond=condc0x7v6w, oldState=true
        04/23/19 20:04:05 devicewatch: device=37, old="1", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="0"
        04/23/19 20:04:06 condchange: newState=true, cond=condc0x7v6w, oldState=false
        04/23/19 20:04:06 evalchange: newState=true, cond=condc0x7v6w, oldState=false
        04/23/19 23:05:49 action: action=Trip
        04/23/19 23:05:49 sensorstate: state=true
        04/23/19 23:05:49 startscene: scene=root.true, sceneName=root.true
        04/23/19 23:05:49 runscene: scene=root.true, sceneName=root.true, notice=Starting scene group 1
        04/23/19 23:05:49 endscene: scene=root.true, sceneName=root.true
        04/23/19 23:05:52 devicewatch: device=58, old="0", name=Front Door Lock, var=urn:micasaverde-com:serviceId:DoorLock1/Status, new="1"
        04/23/19 23:05:53 condchange: newState=false, cond=condc0xphex, oldState=true
        04/23/19 23:05:53 sensorstate: state=false
        04/24/19 07:16:58 devicewatch: device=58, old="1", name=Front Door Lock, var=urn:micasaverde-com:serviceId:DoorLock1/Status, new="0"
        04/24/19 07:16:59 condchange: newState=true, cond=condc0xphex, oldState=false
        04/24/19 07:17:00 devicewatch: device=37, old="0", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="1"
        04/24/19 07:17:01 condchange: newState=false, cond=condc0x7v6w, oldState=true
        04/24/19 07:17:01 evalchange: newState=false, cond=condc0x7v6w, oldState=true
        04/24/19 07:17:03 devicewatch: device=37, old="1", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="0"
        04/24/19 07:17:04 condchange: newState=true, cond=condc0x7v6w, oldState=false
        04/24/19 07:17:04 evalchange: newState=true, cond=condc0x7v6w, oldState=false
        04/24/19 07:19:38 devicewatch: device=37, old="0", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="1"
        04/24/19 07:19:39 condchange: newState=false, cond=condc0x7v6w, oldState=true
        04/24/19 07:19:39 evalchange: newState=false, cond=condc0x7v6w, oldState=true
        04/24/19 07:19:41 devicewatch: device=37, old="1", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="0"
        04/24/19 07:19:42 condchange: newState=true, cond=condc0x7v6w, oldState=false
        04/24/19 07:19:42 evalchange: newState=true, cond=condc0x7v6w, oldState=false
        04/24/19 08:10:23 devicewatch: device=37, old="0", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="1"
        04/24/19 08:10:24 condchange: newState=false, cond=condc0x7v6w, oldState=true
        04/24/19 08:10:24 evalchange: newState=false, cond=condc0x7v6w, oldState=true
        04/24/19 08:10:26 devicewatch: device=37, old="1", name=Front Door Sensor, var=urn:micasaverde-com:serviceId:SecuritySensor1/Tripped, new="0"
        04/24/19 08:10:27 condchange: newState=true, cond=condc0x7v6w, oldState=false
        04/24/19 08:10:27 evalchange: newState=true, cond=condc0x7v6w, oldState=false
        04/24/19 10:15:15 devicewatch: device=58, old="0", name=Front Door Lock, var=urn:micasaverde-com:serviceId:DoorLock1/Status, new="1"
        04/24/19 10:15:16 condchange: newState=false, cond=condc0xphex, oldState=true
====================================================================================================================================
Startup Lua:
       1: 
       2: 
       3: 
       4: 
       5: 
       6: 
       7:

rigpapa · April 24, 2019, 6:21pm

I’m not seeing a problem here. The RS is not tripped because the second condition is false. The second condition is false because the door status is currently locked (1) and the condition requires unlocked (0). It appears that the conditions were correctly met at 23:05:49 and the trip actions ran to lock the door.

Now, because the second condition requires the door to be unlocked (plus options), the ReactorSensor will only show tripped for an instant. As soon as both conditions are met, your trip action that locks the door is run, which causes your lock condition to go back to false, and the sensor to untrip. But that would be correct behavior based on your config and my understanding of your goal.

ubun2Junky · April 26, 2019, 2:54am

rigpapa;
Thank you for your reply. After some testing, it seems that the issues is more with the status of the lock. Vera is not picking up the status of the lock sometimes. The door lock is unlocked and for some reason it shows up as a locked on Vera. It doesn’t happen all the time, but often enough that it’s not reliable. I’m using a Schlage lock, so I’ll ask support and see if there is something I can do. Thank you again!

rigpapa · December 13, 2019, 4:38pm