Zone Type/Night Arming Question

Plugins & Plugin Development DSC Alarm System
1

Hello All,

Just got done setting up an 1832 panel with an envisalink 3 to my Vera. I’m using wireless door and window sensors and am trying to figure out a special use case for one of my sensors. I have a door sensor on the man door of my garage and I’m trying to figure out a way to do the following:

[ul][li]The door should always chime[/li]
[li]During certain hours, when the system is armed (stay OR away), the zone should be bypassed (or at least not cause the alarm to go off)[/li]
[li]During the rest of the day, it should cause an alarm when the system is armed[/li][/ul]

Our UPS and FedEx drivers will leave large packages in our garage and we’d like to be able to leave the door unlocked to allow that without worrying about them setting off the alarm. However, we don’t expect any packages during the night, so it should act like a normal Delay device then.

Is there a way to change zone definitions using LUA code or anything like that to achieve what I’m looking for?

Thanks,
Eric

2

Not sure you can bypass once the alarm is already armed, but if you are not worried about that, then you can create a scene I guess which sets the bypass perhaps using the TPI keystroke function in a luup tab with something like the following:

luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1", "SendCommand", {Command = "071", Data="1KEYPRESS"}, DEVICEID)

Assuming you want to do this for partition 1 then KEYPRESS is going to be the equivalent keypad sequence of something like *101# for zone 1 or *102# for zone 2 etc. DEVICEID will be your device number.

I will test this later, but its going to look something like this:

luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1", "SendCommand", {Command = "071", Data="1*101#"}, 23)

You then marry the above with a timer that does this on a schedule, or have it done as part of an arming scene.

3

OK just tested it from the below HTTP request and it works, so it should also work fine from a luup tab with the other example in my last post

http://10.0.0.12>:3480/data_request?id=action&DeviceNum=23&serviceId=urn:micasaverde-com:serviceId:DSCAlarmPanel1&action=SendCommand&Command=071&Data=1*101#

If you want to test this yourself then you need to replace the IP address and the DeviceNum

4

Thanks for the great example. I’ll give this a shot when I get home later on today.

One more thought…the DSC docs seem to suggest that bypassing a zone only makes it bypassed until the next disarm command is sent. I suppose I could add a trigger to look for disarm events to “re-bypass” during the set schedule, but could I change the zone type to a monitor-only zone during the day instead so I wouldn’t need to worry about this?

Can I do something like:

luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1",
                 "SendCommand",
                 {Command = "071", Data="1*8"}, 23)
luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1",
                 "SendCommand",
                 {Command = "200", Data="(master code)"}, 23)

…then iterate through the zone definition at [001] to change the type to 26 or something for that particular door.

Thoughts?

5

I think it would be risky to go into programming mode in case a button press is missed, or somebody presses something on a keypad at the same time. There is too much risk if screwing something else up.