Try going in your settings and temporarily changing the Envisalink address to some else; save it; wait a few seconds, then change it back to the correct address.
EDIT: just realized the below stuff doesn’t apply since you had it working previously…
Also be certain you have the right password configured. Many people make the mistake of assuming this should be the same one you use to sign into the Envisalink cloud, but it is not. The default Envisalink password is “user”.
I’ve seen simply rebooting my hub will bring offline edge devices back online: I have to do this about once every two weeks for my Roku devices since converting over to that edge driver.
Not elegant but it seems to work for me.
I’m having trouble with initial setup of the driver. It’s my first time setting any edge driver up and I did not participate in the Envisalink 2 test driver channel/phase.
Here’s what I’ve done so far:
TAustin Shared Projects linked from this post
Envisalink 2.1 driver from the channel - confirmed it’s installed see screenshot belowSome things I’ve tried:
smartthings edge:drivers:logcat --hub-address=192.168.0.232
─────────────────────────────────────────────────────────
# Driver Id Name
─────────────────────────────────────────────────────────
1 252d4a5f-d8a4-484b-a15e-7f713737aa31 Envisalink 2.1
─────────────────────────────────────────────────────────
? Select a driver. 1
connecting... connected
Hi. Do you have iOS mobile phone? If so, there is a major platform problem right now with device discovery for LAN devices. Until SmartThings fixes it, you won’t be able to get any devices created.
Being an iOS issue, Samsung is taking their time to get it fixed…
Yes, iOS. Thanks for the info! I’ll keep an eye out for the iOS app update. Is there another thread about the overarching discovery issues?
There’s this… SmartThings CLI: LAN driver logs disappeared
I just posted to try and get status.
This is awesome Todd! Thank you very much for your hard work and effort putting this together! 
Question for you: do you know how come all the zones show up in Alexa (ported from SmartThings) but not the actual DSC panel? I’m trying to automate Arm Stay by integrating with Alexa voice commands but I don’t seem to have access to the actual panel. As a workaround I’m thinking maybe setup a dummy switch that shows up in both and use that as a proxy but wanted to get your feedback first.
Nevermind, please disregard my Q above: seems like I got it working by simply adding a virtual switch.
Only thing though, now I’m stuck trying to figure out why all of a sudden my DSC panel stopped responding to commands, even though it works flawlessly last night. E.g. it shows as “Arming” or “Disarming” but nothing is actually happening. No changes were made, just stopped working all of a sudden. Time to go debug…
2022-10-15T15:51:40.900229787+00:00 DEBUG Envisalink 2.1 RAW DATA RECEIVED: 5020232C
2022-10-15T15:51:40.903123858+00:00 INFO Envisalink 2.1 RX < 502 - 023 - System Error 023
And now it magically started working again on its own! 
Todd,
I have a very strange issue, I have added a new motion sensor to my DSC system and it works correctly. But once added to Smartthings and a routine (use motion to turn on light) is added the motion sensor senses motion when none is present. It is in a walk in closet and even with the door closed the motion sensor is constantly cycling between motion and no motion, it even shows up on the Eyezon App. It stops when I delete the zone from Smartthings. I have swapped the motion sensor with another and the problem persists at the new location.
This sounds like a weird issue I had a week or so ago with one of my regular SmartThings-branded motion sensors. Its battery was supposedly dead, but all of a sudden it started this constant cycling of active/inactive in SmartThings and confusing automations. It didn’t stop until I replace the battery. I’m wondering if there is some kind of bug with motion devices.
Do you mean by this that the constant cycling is also being seen by the eyezon app? If so, could that mean it’s NOT a SmartThings issue??
Yes, but only when the zone is in existence in Smartthings! I have had two weeks of bad dreams over this. I have another motion on the same expansion card that works fine. I have a trip coming up so I will not be able to do anything for the next 10 days. When I have time I will add some additional sensors/reed switches to the alarm panel to check if it repeatable. I did try adding it to a different zone in the alarm, with the same result. It is a real head scratcher!
I just had a trip on the zone so it must be in the alarm system, but I don’t know why it goes crazy when it is connected to Smartthings.
That IS a weird one. I’ll let you know if I think of anything…
Are your zones all contact zones? Alexa will recognize contact-type devices for the ‘IF’ part of a routine. It will only use switches in the ‘THEN’ part of a routine.
I think you’re the first to ask about Alexa integration with the Panel device, and you are right - it doesn’t show up in Alexa for me either. I’m not surprised because the switches that it does have are custom, and the device itself has a category of ‘Security Panel’, which Alexa wouldn’t recognize.
For now, setting up a virtual switch is probably your best bet. You can use one of my vEdge contact devices (has both contact and switch) if you want a device that can be used for both IF and THEN part of a routine.
Hey Nolan - It looks like they have “fixed” the problem with discovery on iOS apps by reverting some software. Try it again and see if it works for you.
Thanks. Just setting up a basic on/off virtual switch did the trick for me. Will keep an eye out but right now things seem to be working quite well 
— Vadim
| TAustin Developer
October 17 |
- | - |
Are your zones all contact zones? Alexa will recognize contact-type devices for the ‘IF’ part of a routine. It will only use switches in the ‘THEN’ part of a routine.
I think you’re the first to ask about Alexa integration with the Panel device, and you are right - it doesn’t show up in Alexa for me either. I’m not surprised because the switches that it does have are custom, and the device itself has a category of ‘Security Panel’, which Alexa wouldn’t recognize.
For now, setting up a virtual switch is probably your best bet. You can use one of my vEdge contact devices (has both contact and switch) if you want a device that can be used for both IF and THEN part of a routine.
TAuston,
I have been using this driver since the summer and have found it to be very reliable and fast. Having all of the DSC sensors available for use in routines locally is very powerful. I thought your DSC Edge Driver would completely eliminate my use of the Eyezon app, however there are some features that I still rely on the Eyezon app for and therefore, I do have some suggestions for some enhancements for your consideration:
Hello and thanks very much for your feedback and excellent suggestions. I hope to have a driver update by the end of the year, so will take all of these into consideration.
Question regarding #1: is the map of user names specific to a particular partition in multi-partition environments, or is it one list pertaining to all partitions?
Based on the “PowerSeries Reference Manual”, I believe it is one list for the system. There are a total of 32 user codes plus 7 “master codes” for a total of 39 access codes. Each can have unique attributes. I’m just reading this from the manual, I’m certainly no expert.
Also, I have a question regarding the attached screen. What does partitionstatus2 and partitionCommand2 refer to? I have only 1 partition which I assume would be partition 1. What does the 2 refer to?
OK, thanks. I’ll have to consider how I would implement this.
The labels you are referring to are actually a problem created by a platform change that happened earlier this year: they made a change that messed up labels for a LOT of drivers. There is fix, which I will implement in my next updated driver.
“partitionstatus2” should say “Partition Status”
“partitionCommand2” should say “Partition Commands”
What you are unfortunately seeing is an internal name for the field.
