AD2PI and Vista20p - Please Help

[kevin]

Please ssh in
Please make sure ser2sock stream is still working as described above

Once you have ssh in, please look for errors in the /opt/alarmdecoder-webapp/instance/logs/ files - if possible, send this file to us at ad2usb@support.nutech.com

Same with the files in /var/log/gunicorn/


If you haven't tried rebooting it, I suggest trying that and seeing if the problem persists. Both log files before and after then would be helpful.

[wideglidejrp]

I also tried with a different browser that would have no cookies or history with alarm decoder.local. Same result. Forbidden. No permission.

[kevin]

Could you please provide the things I have asked? Is ser2sock running and communicating with your alarm and device still? You can verify by telnetting to port 10000 of the alarmdecoder.

Can you provide the logs that are in /opt/alarmdecoder-webapp/instance/logs/ and /var/log/gunicorn/ ? You can do this by SSH into the pi and doing a "sudo su" followed by "tail -n 100 /var/log/gunicorn/alarmdecoder.log" and copy/pasting the results. After this, do a "tail -n 100 /opt/alarmdecoder-webapp/instance/logs/info.log" and do the same copy/paste procedure.

Also please copy/paste the output of this command afterward:
ps axufw

After we have all of this data, we can begin to determine what the problem might be. Are there any settings you had changed prior to the alarmdecoder web-app functioning incorrectly? If no settings were changed, it is possible to save your database and reflash the image to the sd card and restore your database, but this might be a last resort procedure.

[wideglidejrp]

I believe Sean has the data.

[kevin]

Sean did indeed have the data - it would appear your SD Card has perhaps become corrupt. If you would email your address to ad2usb@support.nutech.com we can ship you out a new SD Card with the alarmdecoder image on it ASAP.

Thanks,
Kevin

[scbrews]

The devil is in the detail. The settings have to be exactly right. I would think someone has figured this out and made it work and will share how they did it.

I ran across this thread while looking for something else . Thought I'd close the loop since nobody answered the question. Maybe it'll help someone in the future.
When doing this in the *56 menu mode zone programming, the key item that's used for this type of zone is "Input type" = 2 (aux wired zone) , which is what the AD2Pi is emulating (4219, 4229 Zone Expander Modules) .
Hope that helps
scs