i used this version for alarmserver
basically it uses the api on evl-3 to recieve and send callbacks to smartthings. its pretty complicated and took me a few weeks to figure out.
alarmserver is basically a proxy. evl3 has an api, but only lets one app connect to it (port 4025). so you use alarmserver to stay logged into the evl-3 and forward calls to/from ST cloud. so if your alarm shows an open door, the evl 3 reports code 609, alarmserver gets code 609 and forwards a door open code to ST device. if you look at the code you’ll see every sensor has its own device ID, so when alarmserver sends a callback it sends it for that specific device.
the other integrations floating around didnt work well for me, but they were a great start in understanding how it needed to work. the version i linked has 2 devices called stay and arm. arm is for away arm, and stay is for stay arm. you have to actually port forward out of your firewall though for it to work until some new changes are made so its not super secure.
so heres how my system looks:
dsc alarm -> evl3 -> rpi running alarmserver -> internet -> ST cloud -> smartphone
to arm or disarm, its the exact opposite path
smartphone -> st cloud -> internet -> alarmserver http port (4026 or anything you set) -> evl3 -> alarm system
i actually uploaded all of mine if you want to use it. you still have to manually do oauth and create each devicetype for every sensor, but it made it easier for me in the long run
@ethomasii did you have any headway on making the hub send command via lan instead of across internet yet?