Unable to Arm / Disarm

Hi All,

I just installed the AD2USB and plugin. Configured the plugin using the guide, as well as partitions and zone names.

I can sucessfully see status of my zones and my panel, but i am not able to send commands to my panel.

i can manually arm / disarm / trip sensors on my alarm panel and see the updates in the plugin, but when I try to use the plugin to send commands, nothing happens.

I enabled debug logging and I see this in my live-logging when trying to arm my panel:

02 12/31/13 17:29:37.366 ZW_Send_Data node 14 NO ROUTE (nil) <0x2c311680>
08 12/31/13 17:29:38.947 JobHandler_LuaUPnP::HandleActionRequest device: 45 service: urn:micasaverde-com:serviceId:AlarmPartition2 action: RequestArmMode <0x2f111680>
08 12/31/13 17:29:38.947 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=45 <0x2f111680>
08 12/31/13 17:29:38.947 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:AlarmPartition2 <0x2f111680>
08 12/31/13 17:29:38.948 JobHandler_LuaUPnP::HandleActionRequest argument action=RequestArmMode <0x2f111680>
08 12/31/13 17:29:38.948 JobHandler_LuaUPnP::HandleActionRequest argument State=Stay <0x2f111680>
08 12/31/13 17:29:38.948 JobHandler_LuaUPnP::HandleActionRequest argument PINCode=1234 <0x2f111680>
08 12/31/13 17:29:38.948 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.3166087289177826 <0x2f111680>
50 12/31/13 17:29:38.949 luup_log:42: (VistaAlarmPanel::requestArmMode) Request new arm mode: ‘Stay’, device #45. <0x2f111680>
50 12/31/13 17:29:38.950 luup_log:42: (VistaAlarmPanel::requestArmMode) partNo = 1 <0x2f111680>
50 12/31/13 17:29:38.950 luup_log:42: (VistaAlarmPanel::getPinCode) Using supplied PIN code. <0x2f111680>
50 12/31/13 17:29:38.950 luup_log:42: (VistaAlarmPanel::requestArmMode) Current arm mode = ‘Ready’. <0x2f111680>
50 12/31/13 17:29:39.295 luup_log:42: (VistaAlarmPanel::processIncoming) Incoming data = ‘!Sending.done’. <0x2f5d1680>
50 12/31/13 17:29:39.295 luup_log:42: (VistaAlarmPanel::processIncoming) ERROR: Invalid message. <0x2f5d1680>
02 12/31/13 17:29:39.556 ZW_Send_Data node 14 NO ROUTE (nil) <0x2c311680>
06 12/31/13 17:29:39.694 Device_Variable::m_szValue_set device: 27 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Pulse was: 62 now: 62 #hooks: 1 upnp: 0 v:0x876830/NONE duplicate:1 <0x2c111680>

Any ideas?

Did you activate the new keypad address in the alarm panel programming? I think the AD2USB comes pre configured for address 18.

sigh

Instead of enabling keypad 18, I was disabling it! :-\

Fixed my incorrect programming and it instantly started working…

Thanks for making me re-check!

How do you activate the new keypad address in the alarm panel programming? I recently completed an installation and have the same inability to control the state. I see status instantly. I have also confirmed the ability to change the state using a PC with keypad emulator program.

Here is a link for the vista 15/20p programming manual. you will need the installers code to get into programming mode if different then the default, searching google you can find the the common ones used by the big companys. I would also check the current addresses of your keypads to avoid conflicts, this can be done by disconnecting the battery and unplugging the power supply, then power back up and the addresses should be displayed for the first 30 seconds, if not you may need to find the manual for your keypads, if you only have one keypad its probably address 16 since that is a default in the panel. then go to page 6 to enable the address you want, 18 is the ad2usb default but can be changed using the nutech software. also programming is much easier on a full size alpha numeric keypad, so if your keypad is the smaller type i would use the nutech emulator since that is a full size keypad.