Acknowledging that its a really old panel, maybe it's a good time to ditch the Konnected modules and pick you up a new alarm panel that supports 4G LTE and IP since 3G is getting killed off. Can pickup dual route monitoring for about 25 bucks a month. Then you could use your Envisalink 4 on a supported board. I'm a big fan of the new Vista 21ip and the 6160RF keypad is great for programming it. It only take about an hour to go through all the programming options and then you'll have the programming codes yourself so you can change settings whenever you want.
Thanks for the help! The old DSC has been rock steady since I self installed and programmed it about 13 years ago and since I have some replacement boards for it, Iâm reluctant to replace it (WAF and all, lol). The Envisalink 4 has also worked well and so far without fail and provides me all I need as far as notifications so even if its old school with a new it works for me. I have seen in the forums that using a rpi with the Honeywell panel seems to be solid but I wanted to integrate directly to the Hubitat with the DSC without the rpi and was wondering about the reliability. The KonnectedPro Hubitat integration seems to be currently be supported but all the downsides to the extra wiring needed to add it (the parallel jumpers, limited zones, cost to add zones...I did already order the adapter/integration modules) makes me want to cancel my pre-order...as long as the Envisalink integration is as reliable and just as functional as the Konnected Hubitat integration. I guess I can cancel the Konnected Pro order and try the Integration with the Envisalink first, but I got a pre-order discount on the Konnected Pro and Integration modules and was hoping to get feedback from users with experience using the Hubitat Integration without a rpi. Thanks so much for your reply. I really appreciate it. Have you had any specific problems running your system (with the rpi)? Did you go to using the rpi middleman because of reliability issues linking directly? Thanks for your help!
No issues to report. I just went with the raspberry since it's being actively supported.
With the connected board you'll need a relay to trigger arming and disarming as a key switch as well as an additional relay to trip a zone on the panel if you use sensors in hubitat as additional sensors for your alarm. I pre-ordered a bunch of konnected stuff but after 7 months of waiting I gave up and glad I did. The envisalink works much better for my use cases especially looking back on how I would have had to go about implementing some of the things I wanted. Also gave me the push I needed to get the raspberry which has been helpful for other stuff such as pi-hole, Roomba i7 integration, VPN server, node-red, etc...
Thanks again for your great help and rapid responses! It looks like Konnected will complicate things too much and just Integrating with my Envisalink 4 is the way to go. I was just concerned as it was mentioned that Doug left the project due to âstabilityâ and his integration did not require a rpi. Wasnât clear what that meant.
I'd have to look into it but there are a bunch of users running DSC panels just fine. The developer supporting envisalink might have a better idea of any issues and required work arounds.
@moh [RELEASE] Envisalink App & Driver for Vista/Ademco/Honeywell Alarm via smartthings-nodeproxy
There is a link to the DSC part in this post as well as some additional background info.
Does the rpi based integration also have drivers for the DSC? Also, what model rpi (GBâs needed, cpu version etc) is needed to comfortably maintain the integration with plenty of overhead if I can run the rpi integration on the DSC (or was the rpi only applicable to the Honeywell/Ademcoâs)? Sorry to bother you again but your insight has been very helpful and you obviously have a good amount of experience working with these things! Iâm relatively new to the IP side of HA but have some decades of experience programming old school stuff like JDS Stargate and workstation based stuff like Homeseer (told you I was Old School, lol!). Thanks again!
I'm not sure tbh I haven't really looked into it but I think so. You could read up on it from that link I posted. Or send Brian a pm.
I bought a 4gb RPI 4 but it's way overkill. I also have a 4 8gb one for testing things but it's not really used for anything at the moment. Even a 3 would probably be overkill but the 4 is nice for the desktop speed. Boot time is faster and generally snappier overall. I've been messing around in home automation since x10 and played around with just about everything. I'm still using my ST hub for some cloud integrations with my Honeywell thermostats and my Samsung TVs until ST kills off the IDE. Then I'll mess around with migrating them over.
Thanks Lewis.Heidrick. My house was previously X-10 with Stargate HA control (very old school hence all my questions). Appreciate everything. Iâll check out the thread post you forwarded.
1 Like
Been trying to get Dougâs native DSC/Envisalink compatible integration to work on my new C-7. App loaded with all the drivers and was able to get zones set up in Hubitat and linked to the Envisalink. When I also loaded the Hubitat Alexa Skill, I was able to connect to Hubitat and get the contact sensors to show up on the Alexa App on my iPhone, so I assumed passwords etc were all correct. However, all the sensors showed as closed (and would not update to open) when viewed in Alexa. When I checked their status on the EyesOn web ui, they responded quickly and showed the correct status. So I checked into the log in Hubitat and saw a repeated error âTPI password requiredâ. When I set up the integration app on the Hubitat, I used the password that I use to access the Envisalink device directly (not the registration password for when the Envisalink account was first set up) as IIRC in another thread, the actual Envisalink UI password was the correct one. I also assumed that that was the correct one as both the Hubitat and Alexa were able to download all the sensors correctly. Unfortunately, I still get the ârequires TPI passwordâ error message. Can anyone tell me where I can find the âTPI passwordâ for my Envisalink and which password I should be using (that is, device ui or registration password)? Any help is much appreciated.
Is this the default user user username password?
Hey Lewis. Thanks! When I set up my Envisalink in the UI, I changed the password from the default âuserâ but kept the user name as âuserâ. Since it was changed, I used my new password when identifying the Envisalink to the Hubitat. Perhaps the telnet password doesnât change even when you change the web UI password? I havenât tried the default user/user but Iâll have to give it a try. The only thing is, its odd that both the Hubitat Skill on my iPhone and the Hubitat itself were able to recognize the zones, just not update them as to status. I also wonder if Hubitat is not able to connect since I have the EyesOn web app on my phone. Unfortunately, Iâd really hate to get rid of the EyesOn app since it is rock solid and virtually instantaneous in reporting zone status. I was planning to use my keypads and the EyesOn app as the primary way to arm and disarm (I can voice arm via Alexa through the EyesOn app already), and only wanted Hubitat to access my motion detectors. Thanks as always!
I did some tinkering with the zone names and such when I originally set them up in eyezon and in Hubitat so I could easily identify them. I think the web login is different. Hubitat talks directly to the envisalink as does the eyezon app. Changes to the envisalink are seen by both. Hubitat doesn't update zones automatically because this could break stuff in some instances. The status should update though once you get the correct password in there. Best advice is to get the envisalink setup the way you want and then import them. I use rm almost exclusively to arm and disarm but keypads and the eyezon app are options also. I wanted to reduce false alarms so automating it made the most sense for my uses. The wife and kids are button challenged when it comes to the alarm.
@lewis.heidrck,
Thanks so much for your help and patience. I tried both passwords (default and mine for the device) and still get the telnet dropped and TPI password required message. Tried rebooting Hub. Still no joy. I noticed that the âdevice nameâ originally defaulted to âEnvisalinkâ in the integration app. I thought this was the device user name which canât be changed in the Envisalink so I changed it in the Hub app to âuserâ. Unfortunately, there doesnât appear to be a way to change this once the integration app is set up so I may have to bite the bullet and delete then re-install the integration app from scratch. Do you recall if you set the âdevice nameâ (not the âdevice labelâ) to? I realize that you are running a different version of the app on a RPi but was hoping there was some commonality between the two that could help me troubleshoot this.
I don't think it needs a username to connect. Just a password, ip, and port. Make sure to assign an IP on your router so that the ip doesn't change on you in the future. I renamed mine:
Thanks,
I have a reserved IP on the router for the MAC address as the Envisalink doesnât have a way to set a static ip in the software. The native Hubitat integration app does ask for a âdevice nameâ however. Sorry for the bother. Youâve been very kind.
No, I'm just not familiar with the native app. Remove and reinstall may be your best option.
Hey Lewis,
Just wanted to thank you for your help, time and effort spent to help out a new user. Great news, I finally got telnet communication between the native app and the Envisalink. Deleting and reloading the app several times with various parameter changes still resulted in com errors. As I was messing with the password (at least in the native app) my assumption was correct in that the native integration app uses the web ui Envisalink PW that communicates directly with the board. However, nowhere in the support docs for the app does it state that the password is limited to 6 characters. Once I pared down my Envisalink PW to 6 charcters, suddenly telnet comms started working. Next step is to test lagtime etc for sensor trigger to event execution. Anyway, thanks for taking the time to help and welcome a noob. Hopefully, this info may help other noobs trying to use the native app and save them a little trouble. If this info is accurate (maybe I did something else that just accidentally got it working) even though the native app is no longer supported, it would be helpful to add this password limitation in the docs (of course, if this is actually verified). Anyway, I appreciate your help, it helped me learn a lot about how the hub works.
Anytime, I'm pretty active on here so if you need any help with something just ask.
