Here is the tech info:
RaspPi 3 with AlarmDecoder shield.
WebApp version: v0.8.2-0-g0664184
AlarmDecoder version/config:
VER:ffffffff,V2.2a.8.8,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;L2;KE;M2;CB;DS;ER;CR
I have been using the AlarmDecoder Webapp for a couple weeks and when it works, it works great. I have found that after running for a random number of days, the WebApp appears to die. The webpage can be accessed but the keypad never gets past "Loading...". The logging functions do not work either. I tested ser2socket and it is running fine on my shared port. I found the following log here:
Last entry in info.log.1:
2018-08-11 13:17:22,915 INFO: AlarmDecoder Webapp booting up - v0.8.2-0-g0664184 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:222]
2018-08-11 13:17:22,970 ERROR: Error [in /opt/alarmdecoder-webapp/ad2web/app.py:175]
Traceback (most recent call last):
File "/opt/alarmdecoder-webapp/ad2web/app.py", line 168, in init_app
app.decoder.init()
File "/opt/alarmdecoder-webapp/ad2web/decoder.py", line 242, in init
self._discovery_thread = DiscoveryServer(self)
File "/opt/alarmdecoder-webapp/ad2web/discovery.py", line 60, in __init__
sock.setsockopt(socket.IPPROTO_IP, socket.IP_ADD_MEMBERSHIP, mreq)
File "<string>", line 1, in setsockopt
error: [Errno 19] No such device
-rw-r----- 1 pi pi 71238 Aug 11 13:17 info.log.1
-rw-r----- 1 pi pi 0 Aug 12 06:25 info.log
Of course a reboot will fix it. I like the WebApp keypad but I feel that whatever is causing this problem is making it undependable.
Any help would be greatly appreciated!
