DSC Sensor triggering

Plugins & Plugin Development DSC Alarm System
1

I am trying to use the tripping of a DSC vanishing wireless window/door sensor to trigger an action; in my test case, it’s to turn on an exterior light. Ultimately, the action will be to open the gate once I enter a “home geofence” only if the sensor is reporting back the gate is close. I have tried this with both PLEG and creating a scene. The issue I am facing is that the action (turning on the light) either happens (scene) or not happen (PLEG) regardless of whether the sensor is open or close.

I am running firmware 1.7.513, PLEG 7.39. I have a DSC 1832 with EVL-3

With normal scene:
Device/Sensor Name: Zone 01: Entry Gate
Device Trigger: Whenever Zone 01: Entry Gate is closed whether is armed or disarmed
Action: Immediately Front Light Switch On

Under Devices-Advanced-Variables for the sensor, “Tripped” shows 1 when sensor is open and 0 when it is closed. Under devices, the sensor also reflects the correct state graphically (red lines when open, grey when closed). So there’s some indication that Vera is seeing the state of the sensor. I have also tried this with the sensor “bypassed” and “armed”

With PLEG:
Input-Device Properties:
Name: Entry_Gate_State
Device Name: Zone 01: Entry Gate
Device Variable: Tripped
Condition:
Condition Name: Entry_Gate_Status
Condition Expression: Entry_Gate_State == 0
Action:
Condition: Entry_Gate_Status
Front Light switch: SetTarget/NewTargerValue 1

With the “binary” result I am getting, it seems I am missing fundamental (?)

Any inputs/suggestions are appreciated.

2

Please post the PDF output from the PLEG’s STATUS command.

3

Sometime between downloading the PLEG plugin earlier this afternoon to now, the behavior as well as the layout of the plugin seem to have changed.

  1. When I go into the “Program Logic Event” under Devices, the “Control/Inputs/Conditions/Actions/Other…” now appears in a single row under the green banner on the top. When I first downloaded the plugin, it was in the “white space” area underneath listed in multiple rows. I think they appeared just above the “Advanced/Logs/Notifications/Scenes” if I recall correctly…

  2. What’s more significant is before when I click on Scenes under “Control”, it takes me to the scenes list and I can see the conditions/actions I have set up in PLEG and use that as a template to create a normal scene (where I can incorporate a geofence trigger, etc). When I click on “Scenes” now, it says “Program Logic Event Generator is trigger for” and “Program Logic Event Generator is included in”. It seems that what I have set up in PLEG does not show up in the scenes list

With the “new” version, the action now gets executed properly. Now the question/issue is figuring out how to incorporate my geofence I have set up.

4

I’ve went back to the scenes list and created a scene called “Test Scene”. Now it shows up under “Scenes” in the PLEG section.

In the scene, I have the following:

Device: Program Logic Event Generator
Trigger: Program Logic Event Generator has satisfied condition: Entry_Gate_Status
Action: Front Light Switch off immediately

I assume here that the condition name being asked for is the name of the condition that I had created in PLEG earlier. In my case is if the sensor is closed (condition expression: Entry_Gate_State == 0 where “Entry_Gate_State” is as described earlier in my initial post)

I now close then open the sensor with the front light ON. I execute the scene and the front light turns OFF. As far as I can tell the sensor is opened (“Tripped=1” in the variables section for the device). The status report also seems to indicate the last status of “Entry_Gate_State” is false…