alarmdecoder.com

I am having an issue where I am not getting status updates on my ST installation.
In my ventures to troubleshoot the issue, I have realized that the AD Webapp is not updating with status either. FWIW, this was working previously.
I have an AD2PI directly connected to a RasPi. The AD2PI is directly connected to the serial lines in the panel. Power is received via the panel to buck converter regulated to 5V (tested).
I can minicom into the AD2PI from the RasPi and see the ongoing status updates. When a contact status changes it is reflected in the output. I can send commands (ARM/DISARM) via minicom as well.
When I reboot the RasPi and access the AD Webapp for the first time, it shows the current status... and reports correctly for some time ~5 minutes. And then it doesn't update again. When the Webapp is operating successfully (updating) I am getting the status in ST as well. So I think this is a single point of failure... and I'm not exactly sure where to go from here.

Any assistance is greatly appreciated.

Good news bad news thing.

Good news is we have a new system that although in beta with Samsung(SmartThings) works and has 'most' of the features we had on the SmartThings Classic App.

Bad news is Samsung / SmartThings gave notice and shut everything down on the Classic App a month or so ago. They gave little notice for this to anyone so everyone is still scrambling to get moved to the new Samsung platform.

So why does yours work at all? No idea but maybe its still possible to keep it working. If as you say it works after a reboot then stops I would want to see the logs from the webapp to see what is going on. The classic ST plugin used UPNP subscriptions and sent messages to your local hub. Again in the webapp app log it should show any errors.

Your Pi will still work and you can start using it today by adding a $10 ESP32 device programmed with the current flash firmware available on our git project page to a Raspberry Pi port.

The Github page has some details on the steps to setup and get enrolled in the Samsung developer program under NuTech's account. Once enrolled I will receive an email and will accept your developer account and will send you the Keys to program into your ESP32 with the firmware using the firmware 'st' commands 'stserial', 'stprivatekey', and 'stpublickey'. Again this is all explained on the README.MD for the project on github but if you have questions are want to contribute content to the docs please do

Also available now(ish) are the new appliances. I could be pushed into making some more. I just shipped out 10 for beta testers last week.

Best
Sean M.

My main concern is not with ST at all. It is with the Webapp. It appears that when it works, everything else does.
Watching the Live tab in the Webapp, it sees messages for about 4 minutes and then nothing more. At that point the Webapp status panel does not update.
Here is the content of `/opt/alarmdecoder-webapp/instance/logs/info.log`

Code: Select all

2021-01-06 19:35:04,565 INFO: Event: 0505054:0:1:0:0:0:0 [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:521]
2021-01-06 19:35:36,240 INFO: Event: 0044956:0:0:1:0:0:0 [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:521]
2021-01-06 19:35:38,221 INFO: Event: 0044956:0:0:0:0:0:0 [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:521]
2021-01-06 19:36:02,971 INFO: Event: 0525261:0:1:0:0:0:0 [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:521]
2021-01-06 19:36:40,584 INFO: Event: 0505054:0:1:0:0:0:0 [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:521]
2021-01-06 19:37:53,894 INFO: SUBSCRIBE host:192.168.1.59:5000 callback: <http://192.168.1.202:39500/notifynull> timeout: Second-28800 [in /opt/alarmdecoder-webapp/ad2web/api/views.py:243]
2021-01-06 19:37:53,897 INFO: add_subscriber: 944bc8c6-5080-11eb-ad54-b827eb022a7d [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:273]
2021-01-06 19:38:16,960 INFO: UPNPPush_send_notify_event: status:200 reason:OK headers:{'Content-Length': 1203, 'Content-Type': 'text/xml', 'NTS': 'upnp:propchange', 'HOST': u'192.168.1.202:39500', 'SID': 'uuid:944bc8c6-5080-11eb-ad54-b827eb022a7d', 'NT': 'upnp:event'} [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:659]
2021-01-06 19:38:16,970 INFO: Event: 0505054:0:1:0:0:0:0 [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:521]
2021-01-06 19:39:51,874 INFO: Checking for version updates - last check at: 01-06-2021 19:29:38 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:616]
2021-01-06 19:42:54,450 INFO: SUBSCRIBE host:192.168.1.59:5000 callback: <http://192.168.1.202:39500/notifynull> timeout: Second-28800 [in /opt/alarmdecoder-webapp/ad2web/api/views.py:243]
2021-01-06 19:42:54,452 INFO: add_subscriber: 944bc8c6-5080-11eb-ad54-b827eb022a7d [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:273]
2021-01-06 19:47:55,002 INFO: SUBSCRIBE host:192.168.1.59:5000 callback: <http://192.168.1.202:39500/notifynull> timeout: Second-28800 [in /opt/alarmdecoder-webapp/ad2web/api/views.py:243]
2021-01-06 19:47:55,004 INFO: add_subscriber: 944bc8c6-5080-11eb-ad54-b827eb022a7d [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:273]
2021-01-06 19:49:59,874 INFO: Checking for version updates - last check at: 01-06-2021 19:39:51 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:616]
2021-01-06 19:52:54,328 INFO: SUBSCRIBE host:192.168.1.59:5000 callback: <http://192.168.1.202:39500/notifynull> timeout: Second-28800 [in /opt/alarmdecoder-webapp/ad2web/api/views.py:243]
2021-01-06 19:52:54,329 INFO: add_subscriber: 944bc8c6-5080-11eb-ad54-b827eb022a7d [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:273]
2021-01-06 19:57:53,350 INFO: SUBSCRIBE host:192.168.1.59:5000 callback: <http://192.168.1.202:39500/notifynull> timeout: Second-28800 [in /opt/alarmdecoder-webapp/ad2web/api/views.py:243]
2021-01-06 19:57:53,351 INFO: add_subscriber: 944bc8c6-5080-11eb-ad54-b827eb022a7d [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:273]
2021-01-06 20:00:01,898 INFO: Checking for version updates - last check at: 01-06-2021 19:49:59 [in /opt/alarmdecoder-webapp/ad2web/decoder.py:616]
2021-01-06 20:02:54,208 INFO: SUBSCRIBE host:192.168.1.59:5000 callback: <http://192.168.1.202:39500/notifynull> timeout: Second-28800 [in /opt/alarmdecoder-webapp/ad2web/api/views.py:243]
2021-01-06 20:02:54,210 INFO: add_subscriber: 944bc8c6-5080-11eb-ad54-b827eb022a7d [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:273]
2021-01-06 20:07:54,150 INFO: SUBSCRIBE host:192.168.1.59:5000 callback: <http://192.168.1.202:39500/notifynull> timeout: Second-28800 [in /opt/alarmdecoder-webapp/ad2web/api/views.py:243]
2021-01-06 20:07:54,151 INFO: add_subscriber: 944bc8c6-5080-11eb-ad54-b827eb022a7d [in /opt/alarmdecoder-webapp/ad2web/notifications/types.py:273]

2012-01-06 19:39:53 The last message was seen in the Live tab of the Webapp

So there is something going on with gunicorn. If restart that service, as soon as it comes up it starts working. I start seeing updates in the Webapp and the API sees the new status

I ended correcting the issue by reimaging the SD card. I do not know what the underlying issue ended up being.