alarmdecoder.com

Hi,
the alarmdecoder image for raspberry breaks when apt upgraded, can we have a new one built on top of the latest raspbian version?
Thanks

We are transitioning away from traditional images. I suggest using our docker image - you can run it on your own base pi image.

Thanks,
Kevin

I had no idea that a docker image was available, great thanks!

I'm floundering here. Can you point out where this Docker image is? All I can find is the Raspbian image dated from April of last year.

Thanks!

Always check our github for our latest open source software releases
https://github.com/nutechsoftware/alarmdecoder-docker

So excuse the very basic questions (new to raspberry pi and linux in general), but once I execute the install command on the readme in the docker link you provided, do I need to do anything else to get the webapp up and running? What command do I run to get the app running? Does it automatically start when the pi boots up?

To explain where I am in the process a little, I purchased a pi zero w, and added the pins to the GPIO. I haven't hooked the AD2pi into the panel yet, but am trying to get everything set up software wise before I do all of that.

The pull.sh or install.sh scripts will prepare the raspberry pi by disabling all serial consoles etc, download docker for the pi, and either install the long way(install.sh) or download image from dockerhub (pull.sh)

It will then set all parameters required for the container, and run it - it will automatically restart after reboot as well.

You will then just hit https://alarmdecoder.local


Basically, the install.sh is automated manual install, and pull.sh uses a prepared image on dockerhub (saves time vs manual install)

So I was able to install the AD2pi today, and everything seemed to be working. I was able to get in the setup of the webapp, but using the default networked info, it was able to "open the device", the other other items timed out.

So to confirm what I did:
1.Installed Jessie Lite on my raspberry pi zero w
2. added the GPIO pins
3. Ran the docker pull script (I am currently running the install one just to make sure everything was good)
4. hooked up the AD2pi device to the panel and pi
5. booted up and went to alarmdecoder.local on my PC's web browser
6. During setup said it was a networked device, used the IP address of the raspi, and port 10000
7. left everything else as default on the next screen
8. device was opened, but update and communication timed out.

I poked around the forum a little, and tried a couple of things on the manual ser2sock sticky. Doing that I seemed to lose the webapp setup access, and the ser2sock start command failed, and yielded error 1. However, I was able to see some terminal commands come through via this command: minicom -D /dev/ttyAMA0 -b115200.

So now, as stated above, I am running the install script for the docker in hopes that it undoes whatever I did with that ser2sock sticky, restores the access to the webapp, and magically fixes whatever errors there were out there.

I am certainly open to wiping the entire SD card and starting over again if I have screwed something up in the process. Any help would be greatly appreciated (and hopefully integrating it into Smarthings won't be this hard)!

ser2sock should come active by default in the docker image - if you chose to uncheck "Share your device on network" during setup it will disable ser2sock

When test timeouts happen, I suggest checking wiring - you must have all wires connected properly to ad2pi, including power and ground.

Also during setup, you would want to choose "Local Device" as it is local to your house and local to the raspberry pi and in that process choose to share on your network.

What you have effectively done is told it to try to connect to a remote device.

If you find it hard, we do provide a raspberry pi image that you can use instead.

If you want to start from scratch, attach to the docker container and reinitialize the alarmdecoder settings database at /opt/alarmdecoder-webapp/instance/db.sqlite on the docker image. (sudo rm /opt/alarmdecoder-webapp/instance/db.sqlite && cd /opt/alarmdecoder-webapp && python manage.py initdb)

Ok, I was able to determine that my issue was with the serial ports being assigned incorrectly. I plan on writing up a idiots guide to installation (I think I made every mistake possible during setup). This will be more for myself (if this all works well, my parents want the same setup as me), but I will post it to the forums. Thanks for the help!