Honeywell Ademco Vista Alarm Panels Plugin via AD2USB

Plugins & Plugin Development Unmaintained
561

[quote=“almiller, post:560, topic:168766”][quote=“hugheaves, post:558, topic:168766”][quote=“almiller, post:557, topic:168766”]I just installed the latest from the trunk and i am sporatically getting this error:

50 01/04/13 15:51:55.997 luup_log:8: (VistaAlarmPanel::processIncoming) Incoming data = ‘!RFX:0659888,88’. <0x2edae680>
50 01/04/13 15:51:55.998 luup_log:8: (VistaAlarmPanel::processExMessage) Decoded RFX message: serial = 0659888, loop[1] = true, loop[2] = false, loop[3] = false, loop[4] = false, flags.unknown2 = true, flags.unknown1 = false, flags.battery = false, flags.supervision = false <0x2edae680>
01 01/04/13 15:51:55.999 LuaInterface::CallFunction-2 lu_incoming failed [string “-- Required Libraries…”]:798: attempt to concatenate global ‘deviceSerialNo’ (a nil value) <0x2edae680>
50 01/04/13 15:51:58.517 luup_log:8: (VistaAlarmPanel::processIncoming) Incoming data = ‘!RFX:0659888,08’. <0x2edae680>

Any ideas?[/quote]

almiller,

That’s very interesting. Whatever alarm device you have sending this RF message is setting the “unknown2” flag to “true”. As the AD2USB manufacturer hadn’t figured out what the unknown flags do (hence the unknown part :slight_smile: ), I was discarding (with an error message) any messages that had these flags set. However,as I just found out, the code to print the error message is actually broken, so you’re not getting the correct error message.

So, what sort of device is your “0659888”? Maybe we can figure out how we should be handling these messages.

Thanks,
Hugh[/quote]

Hugh,

I am thinking that is coming from my neighbors house - all of my wireless sensors are accounted for… I will ask and see if he will help me figure out which one it is…[/quote]

Sounds good. Let me know if you find anything out. Hopefully your neighbour won’t be too freaked out if you ask him about the messages you’re “sniffing” from his alarm system. :slight_smile:

Anyway, I’ve updated the code in trunk to log the message correctly, instead of throwing the error.

Hugh

562

[quote=“Latz, post:555, topic:168766”]So then I tried:

luup.call_action("urn:micasaverde-com:serviceId:VistaAlarmPanel1", "StorePinCode", "1234", vista_partition_1)

…I changed the PARTITION_DEVICE_# to vista_partition_1 which is the altid for the alarm panel on the Vera. I don’t get any errors like I did before but it still says I need to enter the pin code before it can perform any functions.

Still not working - appreciate any other ideas for things I can try![/quote]

Unless [tt]vista_partition_1[/tt] is a variable declared above that line, that call is incorrect. PARTITION_DEVICE_# should be the device number of the partition device. So if the partition 1 device has numer 23, the code would look like this:

luup.call_action("urn:micasaverde-com:serviceId:VistaAlarmPanel1", "StorePinCode", "1234", 23)

Edit: I updated the instructions in that post: http://forum.micasaverde.com/index.php/topic,7266.msg95479.html#msg95479

563

I also bumped another thread, but is the ad2usb still the best way to connect vera to an ademco vista 20p, or does the EVL-3 that only recently has added interfacability with the vista 20p and some other vista panels a better way to go?

564

[quote=“mcvflorin, post:562, topic:168766”]Unless [tt]vista_partition_1[/tt] is a variable declared above that line, that call is incorrect. PARTITION_DEVICE_# should be the device number of the partition device. So if the partition 1 device has numer 23, the code would look like this:

luup.call_action("urn:micasaverde-com:serviceId:VistaAlarmPanel1", "StorePinCode", "1234", 23)

Edit: I updated the instructions in that post: http://forum.micasaverde.com/index.php/topic,7266.msg95479.html#msg95479[/quote]

Duh I’m so so stupid :-[ Thanks for pointing that out. Unfortunately it still doesn’t work :frowning: says “Cannot Arm/Disarm Without a Pin Code”. Not getting any startup errors and the script is running in Edit Startup Lua Code section. My script looks like yours:

luup.call_action("urn:micasaverde-com:serviceId:VistaAlarmPanel1", "StorePinCode", "xxxx", 21)

I checked my vista partition one device, the ID is 21.

565

There’s a bug in the plugin when not in Secure Store mode: you have to either reload the Luup engine or execute a command putting the PIN code in the appropriate field for the PIN code to be memorized.

566

I don’t understand.

SecureStore is set to 0 at the moment. I’ve set it to 1, clicked ‘Save’ then clicked ‘Reload’. Still doesn’t work?

I thought the purpose of this script was to put the pin code in the appropriate field?

567

SecureStore must be 0 for what you want. After you put SecureStore to 0, either store the PIN code and reload Luup, or execute a command that requires the PIN code.

568

Perfect! Thanks very much, that worked perfectly :slight_smile:

I had SecureStore set to 0 before but it wasn’t working. Seems to work fine now

569

It looks like this wont work with my alarm?

FBII XL-2t

Wish I could find someway to get it work. Any ideas? It sounds like it would be a big process to put in a new panel…

570

The plugin works only with the panels compatible with the AD2USB.

571

hey @mcvflorin the script was working fine but then it started saying ‘cannot arm/disarm without pin code’ again? It was working fine then suddenly stopped :frowning: any ideas what could be going on? As far as I know, I haven’t changed anything.

572

Probably Vera rebooted (power outage?) and the stored PIN codes were lost.

573

I’m trying to trigger events (turn lights on, etc) based on motion sensors tripping. Everything works great when the system is in the “Ready” Status. I see sensors getting tripped in the UI and it triggers scenes/lights as I intend. However, when I change it armed in the “Stay” mode, the motion sensors no longer get tripped, nothing get’s updated in vera’s UI, and therefore it won’t trigger my scenes.

Is there a settings somewhere that I’ve got to change?

I tried searching the forum but couldn’t find any info, so sorry if this has already been discussed…

Any help?

Thanks.

574

@Poe1

That’s normal, I explained why this happens in a previous message in this thread. You may want to try @hugheaves’ version available in trunk. He added several nice features. Unfortunately I didn’t have time to test his new version and update the documentation.

575

Thanks, mcvflorin. I’ll give that a try.

-Cheers

576

I have my vista 20p with 17 sensors working with Vera via AD2USB. The integration is great and I am able to use the sensors for other things in Vera. One last little hiccup. On the UI5 screen, I have the icon for arming and disarming the system which works nearly perfectly. I click arm-stay, it correctly arms. I click arm-night-stay, it correctly arms. I click disarm, it correctly disarms. However, when I click arm-away, the system does an arm-stay instead. Otherwise, things have been running very well.

Any suggestion as to what the glitch might be with arm-away?

Thank you.

577

triangledave,

sounds like the auto stay armed is enabled in the programming menu, which will change away mode to stay mode if no entry/exit door is opened and closed within the delay time. enter programming mode and change option *84 to 0.

578

Awesome! That did it. Thank you.

David

579

Oh, I thought the purpose of the lua startup script was to enter the pin code for me? Does that mean every time there is a power outage or it’s physically unplugged I will have to store the pin code again?

580

It’s the bug I mentioned in a previous post:
http://forum.micasaverde.com/index.php/topic,7266.msg98510.html#msg98510

Upload the attached file to fix it.