I have the AD2PI (v0.8.2-18-g11a2b9c) talking to my Vista 40P Alarm system on Address 05, but it is very slow to load the Keypad, and the Event Log does not seem to be getting many events. Occassionally it will capture one. (It does seem to get the big ones Armed/disarmed, but not the faults)
The Live Log does catch occassional RPX messages from the device:
I can use the Windows app to retrieve the config string from the Alarmdecoder. I can use the web app to view the keypad, send keys to the alarm, and see the log. The issue is that the Alarmdecoder does not seem to receive all the events from the Vista. It reports on some - like alarming and disalarming, but it does not receive all the Fault messages.
It does receive RPX messages. See below from the AlarmDecoder Keypadd App.
I have 3 keypads (plus the alarmdecoder) and the keypads all report "Comm Failure" - but I think that is because I have disconnected the phone line. The other keypads all get the faults, but the Alarmdecoder does not.
The keypad in the WebApp displays "Loading Please Wait" for a long time, and I can prompt it to switch to Ready by clicking keypads and sending a command to my alarm panel, which the AD2PI seems to catch and flip to "Disarmed, Ready to Arm" but then when I move off the keypad to watch the log, or even the Live log, it will repeat the delay when I toggle back to the keypad.
I can also connect via Telnet to port 10000 and send commands to the panel, which also seems to prompt the webapp to catch them and flip to Ready. ??
Does anyone know why all the faults don't get to the Alarmdecoder?
What are the RFX messages from my alarm ?
Here is the output of the log in the Keypad App.
/2/2019 8:11:17 PM Trying to DNS resolve: 192.168.86.39
5/2/2019 8:11:17 PM Trying to connect to: 192.168.86.39:10000
5/2/2019 8:11:17 PM Loding modules. To remove modules use the modules tab under the about menu
5/2/2019 8:11:17 PM Example V1.0 initialized
5/2/2019 8:11:17 PM keypad V1.0 initialized ()
5/2/2019 8:11:17 PM MyStuff V1.0b initialized
5/2/2019 8:11:24 PM Waiting for communication to AlarmDecoder to open
5/2/2019 8:11:24 PM Communicaiton to AlarmDecoder established
5/2/2019 8:11:24 PM Trying to make sure we are not in config mode sending \r\n A Bunch!
5/2/2019 8:11:27 PM Sending '\r\n' to check if in config mode.
5/2/2019 8:11:27 PM The AlarmDecoder not in config mode. Continuing to initialize.
5/2/2019 8:11:28 PM Sending 'V' command to the AlarmDecoder
5/2/2019 8:11:28 PM !VER:ffffffff,V2.2a.8.8,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;L2;KE;M2;CB;DS;ER;CR
5/2/2019 8:11:28 PM Found Version String
5/2/2019 8:11:29 PM Sending 'C' command to the AlarmDecoder
5/2/2019 8:11:29 PM !>
5/2/2019 8:11:29 PM !CONFIG>MODE=A&CONFIGBITS=ff05&ADDRESS=05&LRR=N&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=N
5/2/2019 8:11:29 PM Found and saving Config String
5/2/2019 8:11:30 PM !Reading configuration.
5/2/2019 8:11:30 PM Sending '\r\n' command to the AlarmDecoder
5/2/2019 8:11:30 PM !UART init.
5/2/2019 8:11:52 PM !RFX:1025152,51
5/2/2019 8:11:55 PM !RFX:0372644,00
5/2/2019 8:12:14 PM !RFX:0959364,b8
5/2/2019 8:14:24 PM [10010001000000000A--],0fc,[f727000010fc801008020000000000],"COMM. FAILURE "
5/2/2019 8:14:29 PM [10010101100000000A--],0fc,[f727000010fc011028020000000000],"COMM. FAILURE "
5/2/2019 8:15:44 PM !Sending.done
5/2/2019 8:15:45 PM !Sending.done
5/2/2019 8:15:46 PM !Sending.done
5/2/2019 8:15:47 PM !Sending.done
5/2/2019 8:15:49 PM !Sending.done
5/2/2019 8:15:55 PM [10010001100000000A--],0fc,[f727000010fc801028020000000000],"COMM. FAILURE "
5/2/2019 8:16:29 PM !RFX:0726232,a0
5/2/2019 8:18:07 PM [10010001100000000A--],0fc,[f727000010fc801028020000000000],"COMM. FAILURE "