alarmdecoder.com

I have set up a raspberry pi with the OS installation provided by alarmdecoder. I have the AD2PI installed and am trying to set it up with an Ademco 20P system. I have set the device address to 20 and that is enabled on the alarm system. But when I go to configure it I get timeouts on saving the config and communicating with the alarm system. What am I missing?





Thanks,

Bill

Please make sure your wiring is correct

Also, if you can, please telnet to port 10000 of the alarmdecoder to see if you can see the message stream from the panel (ser2sock). Here you can view the configuration of the device by sending a 'C' command, as well as try to arm and disarm by sending keyboard keys such as 12341 to disarm.


Did you happen to configure this for a local device? Feels like maybe something is conflicting with the ports. maybe ser2sock is running and it's configured for local device.

Kevin, I tried to telnet into the raspberry pi and I get connection refused. I tried telnet "pi ip address" 23 and telnet "pi ip address' 10000. I can ssh into the server without any problem though. Can I ssh into the server and look for the message stream that way? If so, how do I do that?

Wiring is correct and I have verified that there are no breaks in the wire. Also, I thought I configured for network. That is what it is supposed to be right? How do I check to see if that config is correct?

If you are unable to connect to port 10000 I would think that ser2sock isn't running. You can ssh to pi? Try "telnet localhost 10000" while ssh'd in - see if you can communicate with the streams. If not, it sounds like ser2sock itself isn't running.

This is all configured through the 'setup' process - you can go back through setup at any time and change these things no problem. What you want is "Local Device" but "Yes" to "Share on Network" - as the ad2pi is "local" to the raspberry pi - but you want to use it on your network.

Thanks for the help. I figured out the problem(s). It was that I had changed ser2sock to port number. I thought it had to be what I set the web party to 8080 since I already had a web server on the system at port 80. When I changed that to 10000 it started communicating. But then I had another problem in that I had set the Zone Expanders section to Emulate zone expander #1. I have one zone expander installed so I thought that was needed to be checked for it to work. Found out real quick that the system didn't like that as it set off all sorts of zone alarms

My question is when would I want to set Emulate zone expander? Just curious to know how this might could be used.

Thanks,

Bill

Emulating zone expander and relays would be to add "virtual" zones to your panel. It is a way for the panel to support more zones programmed into it - and with the ad2 device you can basically turn anything into a zone.

Kevin, thanks for the feedback and help. I think I have my main questions answered but I do have one more. On the keypad web, there is a box to check to mute sounds. But I don't get any sounds when in the web. Am I supposed to enable something to get sounds through the web app or does this feature not work? Thanks.

On devices that support HTML5 audio, when the keypad beeps the keypad page on the webapp will issue beep audio as well if the keypad(s) you are watching have audio enabled in your panel programming. The keypad text will also flash red at this time.