Idiots install guide (20p, AD2pi, raspi zero, & SmartThings)

[kevin]

If you have that notification setup and are still experiencing a delay, I would surmise that it isn't set up correctly

Can you check your logs to see if there are errors with regard to that notification?

[raidflex]

If you have that notification setup and are still experiencing a delay, I would surmise that it isn't set up correctly

Can you check your logs to see if there are errors with regard to that notification?

There were some errors in the log related to authentication/tokens. I ended up reinstalling the Smartthings app and re-did the notification settings in the Alarm Decoder web-app. Not sure what happen because it was working fine in the past and I have not touched the setup since I originally configured everything. Thanks for the help.

[jasonsf]

Thanks for the great instructions. I'm having an issue with docker that is installed with the pull.sh script. It doesn't seem to recognize some of the parameters added by the script. Here's the error.

do: /etc/init.d/hostname.sh: command not found
Fetching nsenter...
docker: invalid restart policy -v.
See 'docker run --help'.
Starting alarmdecoder container...
invalid value "" for flag --device: bad format for volumes:
See 'docker run --help'.
Failed to run alarmdecoder docker container...

The only difference I can see is that my default os installer put Stretch on my pi3 instead of Jessie. Docker doesn't even seem to recognize the restart option of "unless-stopped"

Any ideas?

Thanks,
Jason

Sent from my SM-G920V using Tapatalk

[kevin]

A very old version of docker comes in the apt repo's for stretch, so there are things that are needed to be done a little different.

Restart policy should be --restart always for the one on stretch

not sure about the volumes portion, check your syntax - I had this working on stretch, all I had to change was restart policy and device
device for ad2pi being /dev/ttyS0 on newest releases.

[jasonsf]

A very old version of docker comes in the apt repo's for stretch, so there are things that are needed to be done a little different.

Restart policy should be --restart always for the one on stretch

not sure about the volumes portion, check your syntax - I had this working on stretch, all I had to change was restart policy and device
device for ad2pi being /dev/ttyS0 on newest releases.

Thanks. I'll play around with the script and see if I can figure it out. I haven't spent a lot of time with docker so I'll have to do some reading. Maybe I can build a new version of docker outside the repo. Otherwise I'll go through the docker run command and see which parameters are failing and try to fix them for the installed version of docker.

Sent from my SM-G920V using Tapatalk

[jasonsf]

I was finally able to get a newer version of docker by first removing existing docker and then following instructions here: https://docs.docker.com/engine/installa ... nce-script

I ran in to problems pulling the latest docker image because I ran out of inodes. Fixed that by switching docker to using the overlay2 driver: https://docs.docker.com/engine/userguid ... fs-driver/

I have the web app running now. Doesn't seem to like loading in the settings that I exported prior to doing this so I'll set everything up from scratch.

I can't get the nsenter docker image running. It gets this error immediately:

Code: Select all

standard_init_linux.go:178: exec user process caused "exec format error"

But nsenter that is installed on Stretch seems to work.
Getting closer to having this running.

Jason

[TheTick077]

I am still working on getting this set up for my parents installation (the AT&T router didn't support UPnP so we had to set up a new one behind it which was a pain in the butt), and had to restart (they forgot the password to the web app and we didn't set up the email config to reset it). So I wiped everything out, and restarted, but am now running into an error when running the docker script:

Get https://registry-1.docker.io/v2/: x509: certificate has expired or is not yet valid

I am assuming this is an issue you must fix on your side, as everything I have tried has failed. If there is something I can do, can you let me know? Thanks.

[kevin]

Are you using the pull method?
Does it successfully pull?

If it pulls and boots and you're getting that message in the browser, perhaps the ssl cert needs to be regenerated?

[TheTick077]

It is during the pull that I get that error.

[kevin]

At what stage? Post the output please