I have recently installed a DSC alarm system using the 1864 panel. I installed Envisalink 3 in order to connect the alarm system to where I can remotely access it. I can currently access the system from the Envisalink website and it works like a charm. However, I’m not having any luck with getting it working with the Veralite which is using UI5. I have the DSC plugin installed and I put in he IP address for the Envisalink. After saving it then it shows up partition 1 and the 17 sensors I have installed. However, underneath the DSC Alarm Panel under devices it says Lua Failure Lua Failure in red and when I try to bypass any of the sensors then it says Device Communication Failure. Also, partition 1 says ready no matter if I have the alarm disarmed or armed. Anyone have any recommendations to fix it to where it communicates properly? Under DSC Alarm Panel I see Pin Options but not sure what that is. I’ve changed my master code from the 1234 it comes as default so not sure where to enter that (if I need to). I had the communication issues before I changed the master code also. Any help is greatly appreciated.
See here for details (note the code is stored, sent and is in back up in plain text so changing it may provide you with a false sense of security).
http://forum.micasaverde.com/index.php/topic,12919.msg95241.html#msg95241
[quote=“Brientim, post:2, topic:179810”]See here for details (note the code is stored, sent and is in back up in plain text so changing it may provide you with a false sense of security).
http://forum.micasaverde.com/index.php/topic,12919.msg95241.html#msg95241[/quote]
Is the code it is talking about the username and password to access the Envisalink by going to its IP address or the code/password I use to log into the eyes-on site? I did what it said as far as adding the interfacepassword and tried the eyes-on password but that didn’t help either.
One thing that confuses me is that under the settings for DSC Alarm Panel it has DSC IT-100 enabled under DSC Interface Module and Envisalink 3 isn’t an option. Also, under Advanced it has rs232 for the variable commUse. It’s connected through Ethernet though. Also InterfaceType under advanced days IT100. Should I change any of those things? I didn’t find a good explanation of all the variables when it comes to Envisalink 3.
The apps uses the TPI password and username and the default is user for both. This can only be changed through the local TPI interface and has no reference to the Eyez-on account information.
2DS was the earlier model of the EVL3 and use same firmware and TPI. Therefore it should be set to 2DS and saved. This will update the Advanced setting InterfaceType to 2DS.
The ComsUse should be rs232. You should only need to set your IP address.
You should also Test your local TPI log on and on the second page on the bottom left it will display if the TPI connection is activity and if so, the IP address of the connected device which should be your Vera. Only one active connection can exist.
[quote=“Brientim, post:4, topic:179810”]The apps uses the TPI password and username and the default is user for both. This can only be changed through the local TPI interface and has no reference to the Eyez-on account information.
2DS was the earlier model of the EVL3 and use same firmware and TPI. Therefore it should be set to 2DS and saved. This will update the Advanced setting InterfaceType to 2DS.
The ComsUse should be rs232. You should only need to set your IP address.
You should also Test your local TPI log on and on the second page on the bottom left it will display if the TPI connection is activity and if so, the IP address of the connected device which should be your Vera. Only one active connection can exist.[/quote]
I changed it to 2ds and now I do not get the lua failure like before which is good. I logged in to the envisaging directly through its IP and the Envisalink TPI Status says Offline. One thing I should mention is I used a LAN to wireless device to connect to the envisalink in order to not have to run a cable to my router. I made it have a static ip for envisalink but I’m wondering if this device between my router and envisaging is the problem…
There are a lot of people to use a wireless connection and as long as the connections are activity and visible across the same subnet, they should be to communicate. However, if there are intermittent communications or the connection is poor, you will probably experience problems.
After you committed the changes have you restarted you Vera?
Yes. It has restarted a few times since I adjusted the settings for it. I’m wondering if I need to unplug the battery from my security system and then unplug the power from the wall and let the system reset. Since last night I’ve been getting a trouble indicator which says Zone Fault but when I push *2 and then * to look at the error it says No Zone Faults or something like that (I’m not at home to verify exactly what it says). I’m thinking while installing some new light switches last night I had to turn off the power to one or more of the keypads in order to work on a light switch and since that time I’ve been getting the zone fault trouble light. Maybe turning off power to the system and back on will fix that and at the same time that will reboot my envisalink so maybe it will get signal after that.
There is two places you must set Network Supervision… I forgot to tell you about the second one which is via the eyez-on portal. See EyezOn - Smart Home Security No Monthly Fees, basically log on, click on your home, in the top right click manage, Check network supervision. You can also reboot the device remotely from here…
The trouble fault is power loss, and as soon as you acknowledge it *2, it should disappear. It keeps it in memory until it is acknowledge. Also check the activity from here to see what it is register for your faults.