Well, assuming you followed the instructions correctly, first make sure you’re using the SmartThings classic app on your mobile device, then go to the “concord 4 integration” smartapp settings and at the top where it says “Which?" make sure you have your Concord 4 Alarm Panel device selected. Then in the Concord 4 Alarm Panel device, click the settings gear icon and make sure IP is the address of your Pi and make sure API password matches what’s in concordsvr.conf
Also, try restarting everything: Power on the alarm panel first and immediately set the Time/Date on the keypad to get rid of the startup error, then power-on the Pi and start python concordsvr.py. You’ll want to do all this fairly quickly, before you get a bus failure because without the Pi/program running, the alarm can’t talk to the automation module and will error out. Then, let the system learn everything. I’m not sure how long it takes, but it’s not instant. After about 10 min or so, open the mobile app and test one of your alarm contacts to see if it updates open/close status.
Ok so I figured out what was wrong about my setup and got Smartthings connected to the Concord 4! Tricky thing is, I’m running into a few more issues:
-The first is that while it does reflect the status of motion sensors/contact sensors/smoke detectors/the alarm system, it seems to do it very delayed. I opened up one of the doors and got the notification about it 45 minutes later. Is that normal?
-Second is that I can’t seem to arm or disarm the alarm system from the smartthings app. It just says “Arming…” and then eventually returns back to "Disarmed’. Same if the system has been manually armed and I try to disarm it via ST.
-Third is kind of a weird one and may not be a problem with the integration, not sure. It seems to think the Smoke Detector has detected something at all times. It doesn’t reflect that in the ST Classic app, but does in both new ST and in Homekit when I use the Smartthings homebridge extension. Everything else reflects in both properly.
The first two issues are likely caused by the same problem, either the PI IP address in the app is wrong, or the API password in the app doesn’t match the config file. I recently switched out my router which caused the IP of my PI to change and I forgot to update it in the app. The alarm panel status would not update even though the contacts appeared to work. Once I corrected the IP in the app everything started working again.
I’m not sure if the Concord 4 Device Hander/SmartApp is compatible with the new Smartthings app, so that may be the problem with the smoke detector.
Tbh you might be right about those- should the IP address be my Pi’s local one (10.0.1.128 for example), or my external one (71.294.261.294 for example)? Wondering if maybe that’s the issue with the alarm not setting properly
Thanks Scott and Others, this setup has been working great for past couple of years for me.
Recently updated Raspian and see these errors in concordsrv.log
2020-06-08 16:50:15,656 [concordsvr.py:logger()] - INFO - ST TX Exception: (“bad handshake: Error([(’’, ‘osrandom_rand_bytes’, ‘getrandom() initialization failed.’)],)”,)url:zone5/closed
The alarm smartapp in ST is stuck at arming. In past this would clear after a reboot by disarming the alarm from panel by code a couple of times, no dice this time.
Thanks much for all the help.
Got the ST huh and notifications are coming in perfectly in sync now! Sweet!
Just two issues left, it seems-
First is that it’s still not arming when I go to “lock” the alarm in the app. Is there anything special I’m supposed to do? I’ve triple checked to make sure the ip setting is pointing toward the local IP for my Pi.
Second is that the smoke detector still perpetually reads “detected” in SmartThings. Notably, it doesn’t do this in the SmartThings classic app, but absolutely shows detected as the status in the graph webpage.
Thank you for your help @dwestall. I went back through and I think I have everything lined up. I am getting “ST TX Failed: 401 url:zone1/closed” etc. I was thinking maybe my callbackurl_base was incorrect in the concordsvr.conf. This may be simple but should this url end with …smartthings.com or should it be …smartthings.com/api/smartapps or other?
I just received an automation model, but now am having issues communicating via a raspberry pi. How does one determine whether the Concord board is a Concord 4 or Concord 4 Express?
Hi @sdozier, any update on using this with the new SmartThings app? I was just forced to migrate and afterwards my arming and disarming would not work. I decided to remove the Concord 4 Device Hander and SmartApp and start over. Now, I can arm and disarm it, but only as a lock. I’m seeing 2 issues:
The SmartThings Home Monitor widget doesn’t recognize my Virtual Contact sensors, even though as a device it reports open/close correctly. The problem is, the widget doesn’t give me the option to ARMED AWAY or ARMED STAY or DISARMED (see screenshot).
Hello folks,
I need your help, I am on the step 21 of the procedure to install and configure smarthings for panel concord 4 and raspberry pi. After placing my URL command as directed on the step 21 and replacing it with my specific client ID (As shown below in the picture). I got a successful response which is correct based on the instructions guidelines but when i click “Authorize” on the image below, I got this error 404 below what could be going on? any ideas what could be the issue?
