Brientim, i would like to send the command *1 9 9 # to my dsc so it will recall the bypassed zones, and then be able to send the stay arm command. I think the easiest way is to do a luup code, but im not sure how to write it, i will apreciate if you could help.
For a 2DS/3DS, the same technique outlined in this post should work:
http://forum.micasaverde.com/index.php?topic=5154.msg76090#msg76090
luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1",
"SendCommand",
{Command = "01", Data="*199#"}, 70)
Im writing the code like this but its not working, the command I try to send is * 1 9 9 # , will someone please help 70 is my device number
Thanks
The Command is still “071”, it shouldn’t be changed to “01” as you’ve done in the snippet above.
The “071” command stands for:
“Send Keystroke String (Max: 6 Keystrokes)”
and it’s parameter (Data) represents the key-press string you want to “send” to the Panel.
Thanks guessed but even I wrote the code like this luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1",
"SendCommand",
{Command = "071", Data="*199#"}, 70)
The panel does nothing… any clues?
You might have to look at the log files on Vera itself, to see if we’re emitting any errors when you’re making the request. In theory, it should work just the same as the PGM controls, but I’m not sure if the 2DS/3DS does anything special to what’s being asked.
My Dev/Test DSC is powered down in a box, so it’s not easy for me to try it out.
[quote=“petequintanilla”]Thanks guessed but even I wrote the code like this luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1",
"SendCommand",
{Command = "071", Data="*199#"}, 70)
The panel does nothing… any clues?[/quote]
I have never had a requirement to use this function on the panel but my understanding was this would be only recalled if activated bypassed zones using *1 00 which sets all zones to active first. Then sending *1 99 recalled the previous bypassed zoned and set them back to bypass state.
I have got home and tested the code which failed to implement any action on the panel and to enable the function to be called, I tricked the panel by included a longer string which was effective.
luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1",
"SendCommand",
{Command = "071", Data="1#*199#"}, 175)Updated
Included exit hash (the last #) as per post below.
1# is just used as an initial keypress that wakes the panel with the # returning to the main menu.
Thanks, this did the job.
Its takes like 20 seconds the panel to achieve the command, but theres nothing a delay for the stay arming can’t fix.
Thanks again!
I noticed, I removed the exit hash. As this hold the panel input open, is there any difference if it is sent?
Great with the end hash, no delay… everything its working as i like… thanks for your help!! 
Hi Brentim,
I did try to follow your solution but it’s not working for me.
I tried to test the send function and created that (for easy checksum calculation):
luup.call_action(“urn:micasaverde-com:serviceId:DSCAlarmPanel1”,
“SendCommand”,
{Command = “071”, Data=“1”}, 24)
According to logfile:
08 08/26/13 19:14:09.582 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: e[36;1mRunLuae[0m <0x2cef3680>
08 08/26/13 19:14:09.582 JobHandler_LuaUPnP::HandleActionRequest argument Code=luup.call_action(“urn:micasaverde-com:serviceId:DSCAlarmPanel1”,
“SendCommand”,
{Command = “071”, Data=“1”}, 24) <0x2cef3680>
20 08/26/13 19:14:09.583 LuaInterface::StartEngine 0x7ed1a8 device 0 <0x2cef3680>
10 08/26/13 19:14:09.583 sbrk JobHandler_LuaUPnP::HandleActionRequest from IP:255.255.255.255 pMem 0xa53000/10825728 diff: 3497984 <0x2cef3680>
08 08/26/13 19:14:09.584 JobHandler_LuaUPnP::HandleActionRequest device: 24 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 action: e[36;1mSendCommande[0m <0x2cef3680>
08 08/26/13 19:14:09.584 JobHandler_LuaUPnP::HandleActionRequest argument Command=071 <0x2cef3680>
08 08/26/13 19:14:09.584 JobHandler_LuaUPnP::HandleActionRequest argument Data=1 <0x2cef3680>
50 08/26/13 19:14:09.585 luup_log:24: DSCAlarmPanel: debug Action::SendCommand: 071 Data:1 <0x2cef3680>
25 08/26/13 19:14:09.585 luup_io_write 24 size: 6 <0x2cef3680>
51 08/26/13 19:14:09.586 0x30 0x37 0x31 0x31 0x43 0x39 0xd 0xa (e[36;1m0711C9\r\ne[0m) <0x2cef3680>
25 08/26/13 19:14:09.586 luup_io_write 24 result: 1 <0x2cef3680>
10 08/26/13 19:14:09.587 UPnPCallbackEventHandler action RunLua request done pMem 0xa53000/10825728 diff: 3497984 took 0 <0x2cef3680>
52 08/26/13 19:14:09.612 0x35 0x30 0x31 0x39 0x36 (e[32;1m50196e[0m) <0x2d920680>
50 08/26/13 19:14:09.613 luup_log:24: DSCAlarmPanel: debug processIncoming:: Command=501, Data=‘’, Checksum=96 <0x2d920680>
50 08/26/13 19:14:09.613 luup_log:24: DSCAlarmPanel: debug Panel::Command Error <0x2d920680>
there is a checksum error - for string: x30 0x37 0x31 0x31 0x43 0x39 0xd 0xa check sum should be 0x42 0x39 and not 0x43 0x39, is that right?
I’m using IT-100 and DSC Alarm Panel Plugin (0.38).
Regards
@LoWang,
See the second post in this thread.
The Plugin is constructing the correct command, it’s just that the IT100 doesn’t understand it (since it’s a a 2DS/3DS specific command). You may be able to use the original post referenced to “work out” a mechanism for an IT100, but it will be a lot more complex to do, based upon how the IT100 handles keypad simulation mode.
after I posted the message I did realized that (2DS), anyway I did use command 070 for IT100 and got the result I needed,
but it accept only 1 virtual button press at the time.
Is there a (known to you) way to read the bypass zone state - using 070 command toggles the bypass state?
Thanks
[quote=“LoWang, post:14, topic:176385”]Is there a (known to you) way to read the bypass zone state - using 070 command toggles the bypass state?[/quote]That functionality is not available in the IT100, nor the Envisalink adapters, at least AFAIK. The status-request doesn’t give back that level of information.
I am trying to issue a “previous bypass” command too…did anyone have success using the IT100?
/Z/
For IT100 you’ll need to send 5 keystrokes with command 70 (not 71 as for 2ds).
I’m using:
luup.call_action(“urn:micasaverde-com:serviceId:DSCAlarmPanel1”,
“SendCommand”,
{Command = “070”, Data=“*”}, Alarm ID)
luup.call_action(“urn:micasaverde-com:serviceId:DSCAlarmPanel1”,
“SendCommand”,
{Command = “070”, Data=“1”}, Alarm ID)
luup.call_action(“urn:micasaverde-com:serviceId:DSCAlarmPanel1”,
“SendCommand”,
{Command = “070”, Data=“9”}, Alarm ID)
luup.call_action(“urn:micasaverde-com:serviceId:DSCAlarmPanel1”,
“SendCommand”,
{Command = “070”, Data=“9”}, Alarm ID)
luup.call_action(“urn:micasaverde-com:serviceId:DSCAlarmPanel1”,
“SendCommand”,
{Command = “070”, Data=“#”}, Alarm ID )
where “Alarm ID” is my alarm device.
I also have an IT100 with a DSC 1832. We have a wireless sensor on the boathouse and garage which are a bit of a distance from the receiver. In extremely cold weather they sometimes fail to check in and leave the zone open. A minor inconvenience when we are home however it has tripped the alarm on one or two occasions when we are in FL and then I can’t rearm the alarm without physically sending someone to play with the sensor until it checks back in or wait a day or two and hope it fixes itself. I have a number of scenes that will run only when the system is armed so it becomes a big pain when I can’t re-arm
If I am understanding this thread, if I were to set the alarm using the keypad to bypass both those zones at least once, then could I script a luup scene like LoWang has done that I could run to recall those two zones into a true zone bypass which would allow the system to re-arm?
Second issue - the newest firmware has been excellent at reducing the number of disconnects from the panel to about 2 per year. I have the wiznet plugged into a zwave receptacle which allows me to reset the system remotely and it works like a charm - the only challenge is knowing when the panel stops communicating - is there any possibility of adding a notification option to the plugin so you know when this happens or a bit of code to accomplish this?
How about fixing the communication issue with the sensor using a repeater perhaps?
http://www.homesecuritystore.com/p-1952-ws4920he-dsc-wireless-repeater-module.aspx
Hi Strangely,
We actually considered a repeater but the challenge is sensor are the same distance from the keypad but in opposite directions so we would likely need two. Considering the problem only arises 2-3 times per year it didn't seem to justify the cost. We can bypass if you at home or wait until the sensor checks back in while away.
It would give greater piece of mind if we could create a scene to that could remotely bypass the two zones and re-arm again immediately. If it's simply impossible with the IT100 we may look at the 2DS/3DS alternative.
I also wondered if the DSC branded ethernet adapter/interface has the same capabilities as 2/3DS? They are both about $100 bucks on Amazon which is why I was curious.