@ThomasTrain Thank you very much for your kind help. After got your response, I was about to do the upgrade from 2.1 to 3.1. Then I found out that I could switch the driver again in the ST App. As soon as I switched the driver back to 2.1, it works again! It seems ST was stuck on 3.1 driver after the power loss and it would not switch to 2.1 the day earlier (guess my setup is all based on 2.1).
As you suggested, I will find time to do the upgrade to avoid future failure…Thanks again!
Hi everyone, hoping for some help. I have a Envisalink device I am pairing with my DSC 825. I have the main app working, but am having trouble integrating it to ST. I installed the 3.1 drivers and added my alarm system panel. I updated my 4 digit code. I have configured my 8 zones. I only have one partition, so I left that field alone. The IP address has been updated and confirmed to match the actual internal IP. I have tried adding it with the default “user” password, as well as my web password (including the first 10 characters of it). I have also done a reset of the password on the Envisalink to default through the web interface.
No matter what I do the devices remain offline. I had previously linked it to Google Home, but have removed the link as ST offers more functionality.
Any ideas why it is offline? Below is what I see.
| Time | Device Label | Device Name | Location | Component | Component Label | Capability | Attribute | Value |
|---|---|---|---|---|---|---|---|---|
| 2024-04-30T13:27:54.000+00:00 | DSC Primary Panel | DSC Primary Panel | Home | main | Primary Partition | partyvoice23922.partitionstatus3a | partStatus | Offline |
| 2024-04-30T13:27:45.000+00:00 | DSC Primary Panel | DSC Primary Panel | Home | main | Primary Partition | partyvoice23922.dscselectswitch3 | selection | Arm Away |
| 2024-04-30T13:27:45.000+00:00 | DSC Primary Panel | DSC Primary Panel | Home | main | Primary Partition | partyvoice23922.partitioncommand3 | partitionCommand | null |
| 2024-04-30T13:24:36.000+00:00 | DSC Primary Panel | DSC Primary Panel | Home | main | Primary Partition | partyvoice23922.partitionstatus3a | partStatus | * Login failed * |
EDIT - Updating as I fixed the issue. With the EVL4 MAX the default password is the last 6 digits of the MAC address, not user. I found the solution here: Local network access user/user login does not work - EyezOn Forum It is now connecting - time to explore! Thanks!
Is there functionality in the driver to perform an auto-bypass for any zones that aren’t ready when attempting to arm the system?
@TAustin hi - asking this question again.
Is there any functionality to perform an auto-bypass for any not ready zones when arming?
Doing a lot of troubleshooting over here on this one. I had it all working, and then ‘poof!’ it stopped one day, and I just can’t seem to get it to get the DSC to reconnect to SmartThings for the life of me via this driver. I am hoping someone can run through my list of what I tried and highlight anything I should check again or give me an idea of things I could test or isolate; I am open to literally anything!
Local Network Access I can connect directly to the Envisalink through a browser and through the EyezOn app, no problem there. (Although, the port # of 4025 does NOT want to connect through the browser; if I just have to put in the IP address, it works. The IP address alone without the port was working in the app before it stopped so I’m assuming okay here).
Network Both the SmartThings hub (new version) and the DSC are connected via LAN to an Eero router. Both the SmartThings hub, along with the DSC have IP addresses reserved. Again, both the SmartThings hub and the DSC reliably accessible via a browser and their respective ‘apps.’
Drivers I’ve enrolled the hub in the driver channel (I have two hubs, one in the fridge and one standalone). The driver is added to the primary standalone hub (along with every other device). When I’m adding the DSC, I’m always choosing the main (right) hub. I’ve also tried removing/re-enrolling/reinstalling the driver multiple times on the device and that doesn’t seem to make a difference.
Adding the DSC to SmartThings I have no problem getting SmartThings to create the Device when I put it in discovery. Each time, I put in the IP (checking it numerous times, ensuring that the IP is accessible in the browser and copying it over). I’ve tried it with/without the port too. I’m confident the password is correct as it’s the last 6 of the address and it’s what I use to log into the panel from the browser. I have 16 zones which I’ve mapped in the ‘settings’ section.
Multiple Connections? I have an EyezOn App, and at one point, I had a Raspberry Pi supporting the connection. One question: does the DSC only support one connection somehow? Doesn’t seem likely as I can connect multiple devices/browsers just fine via the IP, but thought I’d ask.
Reboots/Restarts SmartThings Hub and the DSC have been rebooted many, many times (even before I started tinkering). I’ve unplugged it numerous times (both devices). I’ve rebooted a bunch of times through the SmartThings ‘advanced user’ interface too.
One thing that might be helpful for me, is there a place I can check logs specifically for this to see where it hangs up? I’m in the Advanced User section of SmartThings on my desktop; I can’t seem to find any logs being posted from the DSC that show the responses as it tries to connect to the DSC.
Open to trying/testing anything. I’m out of ideas. I’ve read the forum from top to bottom, I’ve read the .readme many times and followed everything to a T. Hoping someone can point to any type of ‘gotchya’ I may have missed or point me to a spot I should poke around in more. I’m also open to workarounds. I’m pretty rooted in SmartThings, but if there’s another way (Home Assistant with devices shared with SmartThings?) I’m open to it!
I truly appreciate the work on this project. It was working so well, and I would love to get it back again.
Just got around to installing V3. Much thanks for the great update. We usually enable the alarm to stay instant when we go to bed. I want to be woken up to a siren if someone is trying to get in vs a beeper going off if we are sleeping.
He hasn’t been around for a while, saw it mentioned it another thread, but to answer your question, no option for auto-bypass unless you configure them on the panel as internal zones that don’t get monitored when in stay mode…
I’ve enable STHM and it notifies me when it’s armed but a contact is open.
I’ve also added some routines to notify me if for example, location mode is Away and DSC is not armed.
If you are still having issues, you try CLI to see ST driver logs.
When configuring DSC in ST, make sure no spaces get added after your strings.
If you haven’t already, try turning off your PI to test, but not sure if that will help.