Used AlarmDecoder Rpi Image but can not telnet

[Indy_Larry]

I've used the stock AlarmDecoder Rpi image but for some reason I cannot use telnet. When I try to telnet using the IP address and port 10000 or localhost:100000 I get the following: nodename nor servname provided, or not known
OS - MacOS Sierra
Terminal > Screen > xxx.xxx.xxx.xxx:10000

When I connect a screen to the Rpi I am able to log in and I can also ssh into it.

When I setup the Web gui keyboard I get all green checkmarks

[kevin]

To get this option you have to "Share the alarmdecoder on your network" during local device setup.

[Indy_Larry]

Hi Kevin,

I had the box marked to share it. Could I have the wrong path for the alarm decoder /dev/ttyAMA0?

[kevin]

Make sure your device is at /dev/ttyAMA0 and that your /etc/ser2sock/ser2sock.conf is using the correct device, then restart services (maybe just reboot) - that setting is correct, but maybe it wasn't checked through initial setup and maybe the ser2sock config didn't update accordingly

[Indy_Larry]

Hi Kevin,

Thanks for your quick replies. So I was able to confirm the set2sock.conf file info. Sorry about this but, how can I go about confirming where the device is located?

[kevin]

Kill all services (ser2sock, gunicorn, nginx) and try to attach to the serial port directly

screen /dev/ttyAMA0 115200

exit with Ctrl-A then Ctrl-\

You should see raw device stream at /dev/ttyAMA0 if it is there - if not, maybe /dev/serial0

[Indy_Larry]

Hi Kevin,

After killing those three process and doing the < screen /dev/ttyAMA0 115200 > I was seeing communication to one of my glass break sensors that has been faulting since adding the AD2pi, see attached. Was this what you are hoping to see?

[kevin]

Ok, great - that means it is the proper device.

After killing those services, start them back up in the following order:

ser2sock
gunicorn
nginx

However, a reboot should fix it provided the "share device on network" setting stuck.

[Indy_Larry]

Hi Kevin,

So I did a reboot last night and I still could not telnet into it. So this morning I went through and I re-confirmed the ser2sock config file. It looked the same. I went through and stopped the three services and doing the Screen /dev/ttyAMA0 115200 and seen data scrolling up in the window I followed your other option and instead of rebooting the Rpi I started each service one-by-one Ser2sock, gunicorn, and then nginx. Still no luck being able to telnet in to it.

[kevin]

OK, once you are ssh'd into the pi, try this:

telnet localhost 10000

If ser2sock is running and attached to the device this should work.