I need some help. I’ve tried debugging this myself after reading around on the DSC Alarm Panel page and posts in the forum. I’m stumped as to what I’m doing wrong. Last week I finished getting my new DSC 1832 system installed. Not many zones or very complicated (it replaced a commercial maintained ancient DSC panel). I got an EVL3 which is connected via a TP-LINK TL-WR702N in client mode since I lacked a Cat5 cable at my alarm panel. I can monitor the Envisalink3 just fine over local LAN and via the Eyez-on page.
DSC-1832 (6 wired, 1 wireless zone configured)
Zones all alpha named from RFK-5500 panel
EVL3 with firmware 1.11.135
Static DHCP, so I know the IP address
Veralite with UI5 latest firmware
DSC Panel app 0.40
After I install the DSC app and configure the IP address, the app reloads creating the first 6 zones. It does not retrieve the names (I’ve done the 998 just in case). The app always says it is talking to a IT100, after a few minutes I get “Lua Failure” flags on the Device page and the DSC Alarm Panel goes to a red light. Then I get “device communication failure” if I attempt to set it to Envisalink.
Watching the local EVL3 web server page the network tab always shows that the Envisalink TPI Status is OFFLINE. Not sure if that is supposed to change or not.
You need to change the setting in the Parent Device
's DSC to be Envisalink, This will update the InterfaceType variable to “2DS” do not change to read EVL3.
I have provided some screen shoots for both UI5 and UI7. With Ui5, you will need to save the changes in the top right of your browser and in UI7, chick Save Changes, you should see the message, DSCAlarmPanel : A Restart is required for this setting to take effect. The alternative is to set the directly to InterfaceType variable to “2DS”.
After posting I dug up another post that mentioned using :4025 to force the port number thereby having the app recognize it as a 2DS/EVL3. That also seems to work. Port number :4025 or explicit set to InterfaceType=2DS gets the app behaving better.
However, it still won’t read the zone labels from the panel and populate the sub-devices automatically. Of course I can override this but I thought I would post here for any advice. When I add more zones this will get to a pain later on.
As I was looking for “password” to see how to change the app to match the EVL3 settings I noticed this posted in several places. I also eventually (of course) found the answer to my original question. I need to work on my search-foo!
Maybe eyez-on will eventually change their firmware to support this. At least they are actively developing the module.
Cheers!
Best Home Automation shopping experience. Shop at Ezlo!