The STproxy method is so great & has been rock solid!
Question for anyone… is it normal for the ST app to keep getting login entries?
Yes, that is because it updates state about every 5 mins, and if alarm.com logs the session out it logs in again. You can refresh seconds in settings to zero to turn this off. However, then if you arm or disarm on your panel at home, SmartThings will not reflect the state change, unless you do a manual refresh.
1 Like
That likely means you are using the wrong version of the stproxy for the hardware you are running it on…
Thank you so much. This Edge driver and proxy work great Out of the Box for Windows environment. All there is to do is install the executable and config file and run from the command line once running on same lan as the hub, simply add a device to SmartThings by scanning for new devices and it will automatically add alarm.com interface to the SmartThings app. With the smart app installed, all you need to do is provide your login information in the settings part of the app.
Thank you so much again for this quality work!
1 Like
Welcome! Yes so glad we have this 
can’t thank him enough
@schwark Hi again. I’m finally trying out the stproxy repo solution. You mentioned I need 386 for i686. I only see an .exe file here. If I can find a windows machine to open this .exe file will I be able to transfer some files to my Synology NAS?
@schwark I am still getting this error message on the Windows Proxy output:
2023/01/15 18:49:36 http: panic serving 92.118.39.29:38850: runtime error: index out of range [2] with length 2
goroutine 337 [running]:
net/http.(*conn).serve.func1()
/opt/homebrew/Cellar/go/1.19.1/libexec/src/net/http/server.go:1850 +0xe0
panic({0xd6efe0, 0x1248c120})
/opt/homebrew/Cellar/go/1.19.1/libexec/src/runtime/panic.go:890 +0x21a
main.(*baseHandle).ServeHTTP(0xfd1b70, {0xe07bc4, 0x1260e0a0}, 0x12476300)
/Users/schwark/projects/stproxy/stproxy.go:57 +0x3ec
net/http.serverHandler.ServeHTTP({0x1260e000}, {0xe07bc4, 0x1260e0a0}, 0x12476300)
/opt/homebrew/Cellar/go/1.19.1/libexec/src/net/http/server.go:2947 +0x285
net/http.(*conn).serve(0x12446000, {0xe07d20, 0x12584030})
/opt/homebrew/Cellar/go/1.19.1/libexec/src/net/http/server.go:1991 +0x67d
created by net/http.(*Server).Serve
/opt/homebrew/Cellar/go/1.19.1/libexec/src/net/http/server.go:3102 +0x498
@schwark Just wanted to report I’ve experienced that when trying to arm from the app if your have bypass checked off it will not arm the system. At least for me. Thank you for the great work here.
I had the same issue…bypass setting does not allow the arming commands to work. That said, sensors are bypassed anyways when I arm (regardless of the bypass setting being disabled).
I have successfully set this up using Docker Desktop for Windows. Everything appears to be fine except the current status of sensors. The sensors were added and eventually showed as “Closed” which is accurate. I have left a sensor open for a while and the sensors don’t update their status from “Closed.”
This is the same for me.
I’m sorry, but I was reading the comments and only got more confused. Can someone explain to me how to do this as if I was a child? I have the Smarthings Hub and the ADT alarm system using Z-wave. The sensors, cameras, etc are from Alarm.com.
@schwark sorry to bother again. I have a Synology NAS so I can’t use the 386 solution (it’s a windows executable). Again, uname -m gives me i686. It has an Intel atom processor on GNU linux.
Thanks for any help here!
added a linux-386
1 Like
This has been working fantastically to turn my alarm on / off, but I super wish it could also control the z-wave locks that are connected to my alarm.com panel. Any chance you’ll be offering lock / unlock abilities?
Just installed a new PC and installed the Windows proxy. In addition I completed removed the Alarm.com Panel Driver and all associated sensors. After reinstall of the proxy on my PC, I then reinstalled the driver and reacquired the Alarm.com Panel and sensor devices s.in ST. The alarming and disarming functions work correctly, the sensors are not fuctional, and I am seeing this unending pattern on the proxy terminal screeen:
What am I doing incrrectly?
I wound up moving my locks to smart things. It’s not perfect & a little laggy, but it works.
But now I have a new issue. Apparently my user is at risk of being locked / limited. Anyone else have this?
I installed the stproxy using the newer files (schwark/stproxy) from Gihub on a Linux Ubuntu adm64. The stproxy.service was given proper file permissions were given and it is running as it is evident on the command line from the multiple status lines.
The stproxy does log into alarm.com site since I have enabled the Alarm.com log-in notifications which I receive when I initially run the stproxy-service and then after 5 minutes (300 seconds).
The Smartthings app immediately sees the “device” on port 8081 when the proper credetnials are provided. However, when I hit back and try to refresh the device on the ST app to show the Alarm devices and/or the Alarm status, nothing happens even after a very long wait.
Any input will be greatly appreciated.
Not sure if you solved this problem, but changing the refresh status from 5 minutes (300 seconds) to say minutes may help ease/eliminate the risk of being locked by your security company.
Welp, looks like I can’t disable 2FA in my portal anymore. Seems like the only hope is to see if my dealer can help? I moved houses / have a new panel.