Issues with Smartthings Alarmdecoder (AD2USB 2.0)

General Discussion

Issues with Smartthings Alarmdecoder (AD2USB 2.0)

Postby jplee3 » Mon Apr 27, 2020 5:34 pm

Hey all,

I had an older version of Alarmdecoder running with my AD2USB (older 2.0 model) attached, and it was actually pretty stable and I didn't have many issues with it. Of course, I decided to 'upgrade' and fix what wasn't broken :(

At this point, I've running into several issues:
1) Actually the same issue I ran into the last time I set things up, and I don't recall what the resolution actually was (viewtopic.php?f=3&t=328) but somehow I was able to get things working back then :(

2) I can 'bypass'/ignore issue #1 but after completing the Smartthings installation/integration with Alarmdecoder (followed steps from https://github.com/nutechsoftware/alarm ... martthings), I don't see any activity when I open a door. I've mapped the zone sensor to the virtual contact sensor to no avail. Also strange but the "AlarmDecoder UI" panel thing shows up as "Not Ready" in the classic ST app as well as the IDE, however in the new app it shows "Connected" - either way, I can't seem to get any responses upon testing a sensor. I do have UPNP enabled. Can't seem to get any useful info out of the Live or App logs either.

3) I am able to telnet to the device at port 10000 and even send commands to it no problem. So I'm not quite sure what the issue is.


Where else can I look to troubleshoot all this? As I go deeper and deeper with this, I have less of a tolerance these days than previously when I had no kids and a lot more time hahaha.
jplee3
Junior Nut
Junior Nut
 
Posts: 29
Joined: Thu Aug 05, 2010 8:13 am

Re: Issues with Smartthings Alarmdecoder (AD2USB 2.0)

Postby jplee3 » Mon Apr 27, 2020 8:39 pm

Okay, just grabbed a snippet of log from syslog when trying to run the "Test Device" diagnostic:

Apr 27 21:38:59 AlarmDecoder gunicorn[345]: [2020-04-27 21:38:59,099] DEBUG in discovery: sending message to ('192.168.143.120', 59000): HTTP/1.1 200 OK
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: CACHE-CONTROL: max-age = 600
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: EXT:
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: LOCATION: http://192.168.143.18:5000/static/devic ... iption.xml
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: SERVER: Linux/1.0 UPnP/1.1 AlarmDecoder/1.0
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: ST: ssdp:all
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: USN: uuid:77e5cd76-885d-11ea-94d2-b827eb4c89de
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: #015
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: 127.0.0.1 - - [2020-04-27 21:38:59] "GET /static/img/spinner.gif HTTP/1.1" 200 1094 0.061895
Apr 27 21:38:59 AlarmDecoder ser2sock[1096]: [‼] Closing socket fd slot 2 errno: 0 'Success'
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: Exception in thread Thread-5767:
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: Traceback (most recent call last):
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: self.run()
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: File "/opt/alarmdecoder/alarmdecoder/devices/base_device.py", line 148, in run
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: self._device.read_line(timeout=self.READ_TIMEOUT)
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: File "/opt/alarmdecoder/alarmdecoder/devices/socket_device.py", line 323, in read_line
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: read_ready, _, _ = select.select([self._device], [], [], 0.5)
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: File "/usr/local/lib/python2.7/dist-packages/gevent/select.py", line 77, in select
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: raise error(*ex.args)
Apr 27 21:38:59 AlarmDecoder gunicorn[345]: error: (9, 'Bad file descriptor')
jplee3
Junior Nut
Junior Nut
 
Posts: 29
Joined: Thu Aug 05, 2010 8:13 am

Re: Issues with Smartthings Alarmdecoder (AD2USB 2.0)

Postby jplee3 » Tue Apr 28, 2020 10:30 am

I ended up re-flashing the SD card with Stretch rather than Buster - Buster seemed problematic for some reason maybe with the older device? I don't see why... or maybe I just didn't give it enough time.

Anyway, the sensors seem to be reflecting as expected upon triggering them. In the AlarmDecoder UI panel though, I don't see of a way to ARM the system - I just show two tiles to "Disarm"
jplee3
Junior Nut
Junior Nut
 
Posts: 29
Joined: Thu Aug 05, 2010 8:13 am


Return to General

Who is online

Users browsing this forum: No registered users and 11 guests