Hi There, I’d love to be a beta tester for this. I meet the criteria you out in your post. Thanks.
Hi Josh - Sorry for the delay in responding.
You can access the driver with this channel invite:
Enroll your hub and then click install Drivers, and select the Envisalink 2 driver.
For instructions in how to configure and use, see the readme file here.
FYI, I plan to make some enhancements requested by users and have those available in the next week or two. I’ll post here when the driver update is available.
Great News!!!
With the latest hub update, my envisalink is posting real-time events. I can now dump several zwave pir sensors and use the envisalink pir sensor for automation. I setup routines to make voice announcements on pir motion to monitor when this would happen…
Hi TAustin, it works amazing. Hardly Beta testing - more like enjoying an awesome new feature. Makes the EyezON app obsolete. Thanks for your hard work.
Totally agree. Have been using it for a few months now. Props to TAustin
Any way this Edge integration can be used for a Homebridge plugin?
It would probably have to be re-written for that platform, which I don’t know anything about. One other possibility is to integrate it with Homebridge on Raspberry Pi, since there’s already a (old) Python app called Alarmserver that was designed to run there. Just the SmartThings integration code would have to be switched over to Homebridge.
Today I’m making available a new version of this driver with the following enhancements:
- arm auto-synch from STHM; optionally configured in Settings
With this feature, you can remove automation routines that you may have had to perform this synchronization. However be aware that this is a one-way synchronization only: Changing STHM states can automatically arm/disarm your DSC, but making a change to your DSC arm state will not effect STHM. - addition of SmartThings alarm capability to provide a separate siren indicator
- addition of PGM1 - PGM4 commands that can be sent to the DSC; with the combination of this plus the new siren control, this would allow for triggering a DSC-attached siren with the proper jumpers set on the DSC board
- third ‘no action’ option now available for dashboard button function
- stability improvements to address occasional Envisalink connection issues during driver re-start
I am making this driver available as a new/separate driver and available for install from my regular shared projects channel. So yes, I consider this driver now beyond ‘testing’ phase and suitable for general use (keeping in mind Edge itself is still in beta).
I know home security is a critical function and I do not want to unnecessarily disrupt your setups that are running happily on the current driver. You can continue to use the ‘test version’ of the driver for as long as you need, but do plan to transition to this newly released driver at some point, as all future enhancements will be made to this new version.
Please note that you cannot run the two driver version simultaneously, so when you are ready to transition over, you should delete your partition & zone devices and remove the old driver before you install the new one.
The new driver is available on my regular shared channel with this invite:
Enroll your hub and choose to install the Envisalink 2.1 driver when you are ready. The driver version is: 2022-02-07T18:51:08.394919
Todd,
I bit the bullet and moved to your new driver from the old, a task not for the faint of heart. A word of advice to anyone embarking on this task. Send all household members out to dinner or on a shopping trip and try to convince them to turn off their phones. My wife was complaining about receiving over 30 text messages and the house being broken!
It took me around 5 hours to complete. I took screen shots of all the routines that would be affected (just over 40) and added my “test” sensor to any routines that would auto delete due to all components in them being part of the alarm system.
I would suggest adding a new room beginning with the letter A with all of the devices in it, to make adding them back into routines faster, as it will be at the top off the list.
I used https://my.smartthings.com/ to add the new room as I already have 20, and also for renaming all the devices, copy and paste is way faster on a computer than a mobile phone.
I thought I was done, but remembered I had to activate each sensor to update the status, I have a attic access panel and water drip tray in my attic that will have to wait for me to pull out the ladder during the day.
BTW adding the devices no longer seems to need the 15 sec pause between each one? I had forgot about doing that.
Todd once again thanks for your contribution to the Smartthings community.
I also have some questions for anyone using this driver:
Why if you have a separate alarm system do you use SmartThings Home Monitor?
What advantage/s benefits does this give you?
I ask in all seriousness because as Todd mentioned a home security system is a critical function, and I learnt many years ago that false alarms cannot be tolerated. Which is why I do not use any battery operated devices, use high quality motion sensors and no attempt to use/be pet friendly.
That’s rough! Thanks for reporting your experience. It may not be worth making the change for some that don’t really care about the new features.
I will always keep in mind the potential pain it causes to switch drivers and will continue to look for ways to minimize those issues.
Yes, thankfully that is true, as the Settings issue which had necessitated the pause, has been fixed by SmartThings.
I probably should have made it clear in my announcement post, but one thing that is important to understand about the STHM synchronization: it is only for arm/disarm synchronization and nothing more. If STHM reports any kind of intrusion, leak, etc., it does NOT trigger the DSC alarm. I agree with your sentiment that if it did, it would cause major headaches. My cat is always setting off one of my SmartThings motion detectors which triggers an intrusion alert from STHM, but this does not affect the DSC security system (thank goodness). Some may consider this a shortcoming, but I definitely prefer it this way.
EDIT: with the new PGM command and separate alarm/siren capability, one could set things up with an automation routine (and the right wiring on the DSC board) to trigger your siren upon an STHM alert.
Edit 2:
I’m an idiot. Please ignore my question.
For other idiots, note that you have to enter the Envisalink’s PASSWORD, not Username.
Tod
Don’t know if you’ll remember but I was using the test driver when you added the second partition functionality.
I moved over to the new 2.1 driver this morning, after deleting all devices and panels of the old driver.
After installing the new driver, the new panel was created, but all panels and devices show offline. I started the log for the driver and noticed that the driver fails to log into the Envisalink. Rebooting the Envisalink and the Smartthings hub did not make a difference.
I’m sure I’m using the correct password, as I’m able to log directly into the Envisalink from a web browser (using the IP address and password).
What I’ve noticed is that the Username shows as “User” (capital U) in the list of settings, but opening the username setting, shows. “user” (with a small “u” as it should be").
Any ideas?
Edit:
The username is not the issue. I checked the logs when I change the Username and password - the log shows the username and password exactly as provided in the settings:
2022-02-20T08:42:07.785691598+00:00 INFO Envisalink 2.1 Using config prefs: 192.168.0.22:4025, password: user, alarmcode: ###
Glad you solved it! I thought maybe you still had your other driver running and connected to the Envisalink, but that will do it too! 
BTW, the Settings does capitalize the first letter of the value when it displays it for some reason, but as you pointed out, that disappears when you go to edit the field. I’ve reported it several months ago to SmartThings.
Yea, who would have thought up such a thing…hehe
Hi Tom
Would you mind having a look at the “Stay Arm” procedure for the additional panels? The “Stay Arm” button seems to arm the panel in away mode. At least, that is what the driver/app reports. (According to the Envisalink, the panel also actually arms in Away Mode.) I’ve noticed this with the test drive as well but never got around to making sure that is indeed the case.
Did you make any changes in 2.1 in respect of the commands? After upgrading to 2.1, the following commands don’t work in webCore anymore:
Thank you.
How are you initiating the command: from using the dashboard button? device details button? or an automation routine?
There shouldn’t be any changes needed. Since you are using Webcore, I’m wondering if you re-defined the device in Webcore when you changed drivers and devices? I’m referring to when you have to go in to Webcore->settings->available devices and make sure the new panel devices are selected for access by Webcore. Any chance it is still pointing to the old devices?
I’ve been unable to arm the panel via webCore (the only automation I use). I tried arming it via the Smartthings app “Arm Stay” button, as well as via the partition commands function of the device in the Smarthings app.
Yes, I have redefined the devices in webCore. (I used different Panel names this time around). Edit: I’m able to test the alarm arming state in webCore, but it fails to respond to the arm/disarm commands.
I’ve meant to ask you, is it possible to add the “switch” function to the panel devices? I’m sure that would allow us to use the Panel device in Actiontiles. The panel device doesn’t show up one Actiontiles (at least, I’ve been unable to find it in Actiontiles under any of the options).
As always, thank you for your help and contributions.
Did it work properly this way or no?
Would you be able to capture a log of the arm sequence that is not working for you so I can see what is happening?
They are currently defined as SecurityPanel type devices, and I wouldn’t want to have to omit that. It’s possible I may be able to define multiple categories; let me check on that.
The ActionTiles issue is capabilities, not categories. ActionTiles doesn’t currently support custom capabilities, and I don’t think it supports all of the stock capabilities either. I’m also pretty sure it doesn’t support multiple components. This is really an issue that their team needs to deal with on their end, and they’ve posted a few times with questions that indicate they’re working on transitioning to the new API.
If you put a stock switch capability on your partition device as was requested, then ActionTiles would be able to toggle that switch. It still wouldn’t be able to handle the custom capabilities since those just aren’t supported. Of course, if you put a stock switch on your partition device then Alexa and Google will also see it and be able to control it, which is probably a security concern for some of the people using your integration.
The other option is virtual switches, either created outside the driver and linked via routines or created/managed by the driver. I prefer that solution since it gives users the choice of which arm/disarm commands they expose to Alexa/Google.