I copied this from the Envisalink forum, it is another way to check comm with the device.
Arm Stay: http://username:password@xxx.xxx.xxx.xxx/2?A=1&P=S&p=1
Arm Away: http://username:password@xxx.xxx.xxx.xxx/2?A=1&P=A&p=1
Disarm: http://username:password@xxx.xxx.xxx.xx … p=1&X=zzzz
I was only using a 4 character numeric pw so it wasn’t an issue. I’m going to change it again, do a reboot of the Envisalink4 and keep the :4025 at the end of the IP in DSC Panel settings. I’m guessing it was some hangup with the Envisalink4 not recognizing the password sent from ST.
I’m going to chalk this one up to “did you try rebooting?”
Thank you for your assistance and hard work on this driver. Much appreciated.
I can’t believe someone would design a firewall that way. I get what they were going for, but wow.
You definitely should include the port number in the Envisalink address.
If you learn anything more about the password problem, let me know in case there’s something I need to do in the driver.
@TAustin amazing work but I screwed up 
I was using your driver since couple of months all was perfect. I add a new motion detector on my DSC Pannel. All was fine on envisalink/eyezon but it seems like the driver was not catching/updating the status of that new device.
I went ahead a did the « refresh » partition command from your driver in the partitioncommand2 section. And it seems it has screwed everything. 
Now everything is offline and the edge drivers seams not connected to the envisalink anymore… I try rebooting everything, delete the driver…
Now it seems it stays offline…. , 3 questions :
1st question : what does the refresh command do ?
2nd question : did a new device is supposed to be updated after been added to the driver automatically?
3rd: do you know where I screws up ? 
Thank you for your amazing work !
Yikes! You are in a fine mess
It tells the Envisalink to send a complete data update back to the driver, which is status for each panel device and each zone.
It won’t happen automatically. You have to go into the panel device Settings and set the device type for the specific zone. So if you added a motion device to zone 7, you’d simply change it from ‘unused’ to ‘Motion detector’. Be careful because once you’ve created a zone, it’s rather difficult to change it.
Well if you didn’t actually create the new device for your new zone, then that would be one thing. But it really shouldn’t cause everything to fail and go offline like you described.
Hi there! First and foremost, thank you for creating this. I set it up tonight, have it working but have a question. Where I was previously using the AlarmServer, I was able to use the SmartLighitng app with the open/close sensors that are part of the DSC system. It does not seem that I can with this? Just wondering if I am missing something or if that is a limitation? Thanks again!
The zone devices here use custom capabilities rather than the stock contact or motion sensor capabilities. This allows you to check for an alarm condition as well as open/close/motion/no motion.
That’s why Smart Lighting app doesn’t recognize the devices.
Thank Todd, I’ve been able to fix everything.
FYI, the “refresh command” reset all my wireless sensor… hopefully, I’m mainly wired
Thank again for such a great driver contribution and support to users !
Interesting. I noticed them in smarthome monitor but not in smartlighting. I suppose it could be done with routines instead. Thanks again!
Thank you so much for this, I made the switch away from my alarmserver pi as it suddenly died today and used 2.1 here to switch over and go direct and it all went great! My biggest concern was that somehow a feature of an automation wouldn’t port or something but honestly all I did was delete unnecessary ones I had made as everything else is now right here!
I use the auto sync feature, and then I set up a routine “If the partition status is disarmed for the primary panel Then Disarm the SHM” in case someone disarms with the keypad, but is that necessary?
Thanks again, great work, I’m going to try and find where the horn siren is through the PGM commands at some point, I inherited the system in this house
My DSC alarmserver went down (Groovy no longer working) and installed the edge driver. It was very easy as you said. Thank you so much for this great work TAustin!
Some small observations…The Smartthings Home Monitor has been renamed Home Monitor from STHM. Is this deliberate?
Also Under Security>View Sensors…There is no longer a list of sensors for away or stay modes. Prior we were able to choose which sensors were designated for away or stay. Is this normal?
I am so happy this worked on the first try. Again thank you for all you are doing.
Regarding the STHM integration. Yes, I see it’s been renamed AGAIN…
This driver wasn’t designed with STHM integration in mind, since it has been in a state of change over the last couple years and frankly, hasn’t been very reliable as a trigger. I do have a device setting that you can enable that is supposed to arm the system when STHM goes into stay or away mode, however it has been hit or miss in terms of its reliability. Sometimes the driver just never gets triggered even though STHM itself changes.
I will say that lately it seems to have gotten better. And if it seems to be more stable and reliable, I’ll look at better integration. But right now you can achieve what you want through automations.
I seem to be getting duplicate events (Door open, door open, door closed door closed) for single zone events in the sensor history – did I configure something wrong? Any idea what that might be?
Also, thanks for developing this, being able to quickly get the alarm integration restored on 1/1 after not paying attention to the DTH sunsetting saved my bacon.
They aren’t duplicates- there are two different capabilities (fields) maintained by the driver.
Thanks TAustin for the clarification about the STHM. When I press any of the 3 buttons on STHM on the app, it works or it does not. In addition, when the alarm is used in automation it will not sync with STHM. I have turned on autosync STHM in the driver settings. I assume this is the driver setting you mentioned previously. It would be awesome if future versions you will be able to fully integrate STHM in the driver. I am certainly not complaining and I am very happy with what you have done. Bravo!
Oh you are right, I just needed to read the fine print.
As I mentioned, when you put STHM in arm away or stay, it is supposed to notify my driver, but it doesn’t always work. This is a platform issue.
My advice is to stick with automations that directly arm the Edge driver rather than rely on the STHM synch feature. Hopefully things will improve!
