alarmdecoder.com

Hi
I have raspberry + AD2PI + latest beta firmware installed and connected.
Logging in to rasp via web browser, I can see status of alarm system, get new alarm events...etc

What does not seem to work at present is:
- controlling the alarm system via web browser
- viewing the ip cameras (192.168.20.35/snapshot/view4.jpg) checked to work correctly in web browser.

I have only 1 keypad connected to PC1616 and it shows up as nbr 3 when I enter *8 - 5555 - 903 at DSC keypad

A triggered zone shows up in log as: The alarm system has been triggered on zone (000)!

PC1616 has only 6 hardwired zones and these are showing up in log as nbrs starting with 40

2015-6-26 4:44:32 PM disarm The alarm system has been disarmed.
2015-6-26 4:44:32 PM alarm restored The alarm system has stopped signaling the alarm for zone (000).
2015-6-26 4:44:25 PM zone fault Zone (-44) has been faulted.
2015-6-26 4:44:21 PM zone restore Zone (-45) has been restored.
2015-6-26 4:44:18 PM zone fault Zone (-45) has been faulted.
2015-6-26 4:44:17 PM zone restore Zone (-46) has been restored.
2015-6-26 4:44:16 PM zone fault Zone (-46) has been faulted.
2015-6-26 4:44:15 PM zone restore Zone (-41) has been restored.
2015-6-26 4:44:14 PM zone restore Zone (-47) has been restored.
2015-6-26 4:43:58 PM zone restore Zone (-43) has been restored.
2015-6-26 4:43:48 PM alarm The alarm system has been triggered on zone (000)!
2015-6-26 4:42:29 PM zone restore Zone (-41) has been restored.
2015-6-26 4:42:25 PM zone fault Zone (0) has been faulted.
2015-6-26 4:42:24 PM arm The alarm system has been armed.

IS all above correct or am I missing some configurations.

Thanks for a great product!

/Gerry

Hay Gerry.

Please confirm the beta firmware you are using currently. I just uploaded a new beta last night for DSC and I do suggest you update again.

Also what keypad address did you set for your AD2* In this case its not so much address as partition. Do you have a 1 partition config or multiple partitions? If one partition set AD2* to address 1.

The zone faults you are describing sounds like a bug but I would need to see detailed logs to confirm. First update and if it continues I would need some more data from your alarm.

Re
Sean M

DSC support in the base alarmdecoder library still needs to be fleshed out some, which is why you're seeing the weirdness with the zone faults. I've added it to our TODO list.

Hi Sean,

I used this firmware (http://www.alarmdecoder.com/downloads/f ... 2_2a_8.zip)

PC1616 was defaulted before I connected it to rasp/ad2pi so it has just 1 partition with keypad showing as keypad 3

I originally set ad2pi as nbr 4, now changed to position 1 and now the webapp is working 2-way.

I'll test a few alarms and mail log.

Thanks for the help.

/Gerry

Regarding the IP cameras, can you post your gunicorn log and see if any exceptions are being generated with regard to the camera? On the pi itself it would be in /var/log/gunicorn/

Regarding access to /var/log/gunicorn/.............getting permission denied

Hi All,

Sorry for last post reply .....forgot to use sudo su first

Here is the contents of alarmdecoder.log:

[2015-06-28 06:25:07 +0000] [6451] [INFO] Booting worker with pid: 6451
[2015-06-29 12:26:46 +0000] [2465] [INFO] Handling signal: term
[2015-06-29 12:26:47 +0000] [6451] [INFO] Worker exiting (pid: 6451)
[2015-06-29 12:26:48 +0000] [2465] [INFO] Shutting down: Master
[2015-06-29 12:27:48 +0000] [2423] [INFO] Starting gunicorn 19.3.0
[2015-06-29 12:27:48 +0000] [2423] [INFO] Listening at: http://127.0.0.1:8000 (2423)
[2015-06-29 12:27:48 +0000] [2423] [INFO] Using worker: socketio.sgunicorn.GeventSocketIOWorker
[2015-06-29 12:27:48 +0000] [2451] [INFO] Booting worker with pid: 2451
[2015-06-29 12:28:36 +0000] [2451] [ERROR] Exception in worker process:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/gunicorn/arbiter.py", line 507, in spawn_worker
worker.init_process()
File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/ggevent.py", line 192, in init_process
super(GeventWorker, self).init_process()
File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py", line 124, in init_process
self.run()
File "/usr/local/lib/python2.7/dist-packages/socketio/sgunicorn.py", line 80, in run
**ssl_args
File "/usr/local/lib/python2.7/dist-packages/socketio/server.py", line 72, in __init__
address = args[0].cfg_addr[0]
AttributeError: 'socket' object has no attribute 'cfg_addr'
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/gunicorn/arbiter.py", line 507, in spawn_worker
worker.init_process()
File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/ggevent.py", line 192, in init_process
super(GeventWorker, self).init_process()
File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py", line 124, in init_process
self.run()
File "/usr/local/lib/python2.7/dist-packages/socketio/sgunicorn.py", line 80, in run
****************************************************************
contents of alarmdecoder.log.1:

[2015-06-27 06:25:09 +0000] [4358] [INFO] Booting worker with pid: 4358
[2015-06-28 06:25:05 +0000] [2465] [INFO] Handling signal: usr1
***************************************************************

NOTE: I added a second camera - same manufacturer (Grandstream so http string is the same for both cameras and FULLY CHECKED in different browsers).....still no images showing (even after a reboot). Each image is showing up as the broken link icon. I copied the link and tested in web browser with this result:
web browser link: https://192.168.20.86/static/cameras/ca ... 5583757017
page response:
404 Not Found
nginx/1.7.4

2nd camera web browser link: https://192.168.20.86/static/cameras/ca ... 5583847784
same result as first...404 Not Found nginx/1.7.4

Anything else I can do to assist here?

/Gerry

If possible, could you please email ad2usb@support.nutech.com and get us some SSH access to poke around and nail down the reason this isn't working?

All right, the issue seems to stem from the particular version of OpenCV library no longer containing a couple of constants that the code uses. Silly moving targets.

specifically: cv2.CV_LOAD_IMAGE_COLOR and cv2.cv.CV_HAAR_SCALE_IMAGE - these no longer exist in the library as constants so we will have to update the code to accommodate that

If you would like in the meantime you can edit /opt/alarmdecoder-webapp/ad2web/cameras/types.py

replacing cv2.CV_LOAD_IMAGE_COLOR with the value 1 and replacing cv2.cv.CV_HAAR_SCALE_IMAGE with value of 2

Do note that this will break your updates until you revert your change after we push up a fix.

Thanks Kevin,

I made the changes and both cameras are now working...........
However I have now noted a 5 to 10 sec delay when sending and receiving data between alarmdecoder and the PC1616.
When 1 camera is installed the response delay is approx 5 secs
Adding a 2nd camera increases this response delay with another 3 - 4 secs

Also noted:
refresh rate on camera page increases based on amount of cameras....approx refresh rate is 10 - 12 secs for one camera,
when the 2nd camera is added the refresh increases to 16 - 18 seconds per camera.

When I remove the cameras the response delay between alarmdecoder and PC1616 disappears.

Rasberry Pi info:
processor : 0
model name : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS : 2.00
Features : half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb76
CPU revision : 7

Hardware : BCM2708
Revision : 000e
Serial : 000000002ff4a7c0

I am using 2 models of Grandstream IP cameras which only offer either H.264 or MPEG. Both cameras are set to MPEG and the URL is
http://192.168.xx.xx/snapshot/view4.jpg

/Gerry