SmartThings DSC/EnvisaLink Integration [DEPRECATED]

Devices & Integrations
203

on the UI it shows me this
Type:EVL4 HW
Version:190

204

First off I can see that you’re integrating it with Honeywell (as opposed to DSC which is what I have) but I don’t think that’s an issue.
But what I do see is that I’m running version 130 on my end which seems to be very much out of date; so that might explain the disparity. I’ll attempt to update it and report back on the results - hopefully they line up with what you’re seeing on your end.

— Vadim

| Weko_Altamirano
May 10 |

  • | - |

on the UI it shows me this
Type:EVL4 HW
Version:190

205

So I’ve updated the firmware for my EVL to the latest available version (176) and the driver is still working fine for me. I did notice however that I have “EVL4 DSC” under “Type” so I think this is where the difference resides; the EyezOn interface is different under EVL + Honeywell integration, it seems.

206

gotcha many thanks for looking into it, wonder why they decided to change the interface for honeywell, well in any case got it working if anyone wants it but the code is very brittle and may break again if they change the interface, had to add another property for system name, here is what I got

if (textData.contains("${settings.partName} : <span style=\"color:green;\"> Ready") 
    	|| (textData.contains(settings.systemName) && textData.contains(">Ready </span>"))) {
        systemStatus = STATUS_READY()
        sendEvent(name: "switch", value: "off")
    } else if (textData.contains("${settings.partName} : <span style=\"color:black; \"> Busy") 
    	|| (textData.contains(settings.systemName) && textData.contains(">Busy </span>"))) {
        systemStatus = STATUS_BUSY()
        sendEvent(name: "switch", value: "busy")
    } else if (textData.contains("${settings.partName} : <span style=\"color:orange;\"> Exit Delay") 
    	|| (textData.contains(settings.systemName) && textData.contains(">Exit Delay </span>"))) {
        systemStatus = STATUS_EXIT_DELAY()
        sendEvent(name: "switch", value: "exiting")
    } else if (textData.contains("${settings.partName} : <span style=\"color:red;\"> Away Armed") 
    	|| (textData.contains(settings.systemName) && textData.contains(">Away Armed </span>"))) {
        systemStatus = STATUS_AWAY_ARMED()
        sendEvent(name: "switch", value: "on")
    } else if (textData.contains("${settings.partName} : <span style=\"color:red;\"> Stay Armed") 
    	|| (textData.contains(settings.systemName) && textData.contains(">Stay Armed </span>"))) {
        systemStatus = STATUS_STAY_ARMED()
        sendEvent(name: "switch", value: "on")
    } else if (textData.contains("${settings.partName} : <span style=\"color:red;\"> Night Armed") 
    	|| (textData.contains(settings.systemName) && textData.contains(">Night Armed </span>"))) {
        systemStatus = STATUS_NIGHT_ARMED()
        sendEvent(name: "switch", value: "on")
    } else if (textData.contains("${settings.partName} : <span style=\"color:red;\"> Armed Zero Entry Delay") 
    	|| (textData.contains(settings.systemName) && textData.contains(">Armed Zero Entry Delay </span>"))) {
        systemStatus = STATUS_ZERO_DELAY_ARMED()
        sendEvent(name: "switch", value: "on")
    } else {
        log.error "Unable to determine system status from response: ${textData}. Setting to Unknown."
    }
207

FYI current version of the handler code is broken due to a recent EyezOn Portal UI refresh. I’ve updated the code in GitHub to get it working once again so you will want to update your local handler from there, if it stopped working for you.

208

@vadimb, yup! The eyezon website looks to have been updated as you mentioned. I just came here to post about that, but looks like you already knew, and udpated your code. I will update my handler code as you suggested. THANK YOU!!!

209

No problem. Enjoy using it for a couple more months before they break it for good :slight_smile:

— Vadim

| hevykevy420 Kevin
October 10 |

  • | - |

@vadimb, yup! The eyezon website looks to have been updated as you mentioned. I just came here to post about that, but looks like you already knew, and udpated your code. I will update my handler code as you suggested. THANK YOU!!!

210

Copied code from github, and it looks like I’m back up and running. Tested EVL4/Vista15p arming Away manually from ST mobile app, and also arming my Night Max mode via scene command triggered by Alexa. I will also test my geofenced Alarm Away command, using the stock ST geofencing abilities…but if the device buttons are working…my linked scenes and triggers should work just fine. My wife thanks you @vadimb !!! :slight_smile: