EyezOn Forum

Anyone here using the EVL3 module in a DSC Alarm with Indigo Home Automation software? I'd like to have alarm events trigger actions in my Indigo software to control Insteon and Zwave devices, but the Indigo DSC Alarm plugin doesn't get all of the necessary information i.e. no Zone status info and and keypad is always in disarmed state. Is this a limitation of he EVL3 module? Any help is greatly appreciated!

I have it working with the E3 with Indigo and the DSC plugin. I am assuming you have your keypad and zones defined per the install overview from the plugin author. One of the things that made me scratch my head a little with this plugin was I had changed the password on the E3, and used a password longer than 6 characters (the E3 apparently has this limit, and automatically truncates the password you enter in the web interface). If your password is longer than 6 characters, try using a password of only the first six (or change it to a 6 char password) and check the Indigo status log to ensure the plugin is authenticating correctly. It's also a good idea to assign the E3 a static IP address if you haven't done that, as it can change on DHCP renew requests.

Your log will have error notices similar to the screenie below. That was the only issue I ran into with setup, and it's working like a charm for me with the latest E3 firmware, Indigo 6, and the DSC Plugin v1.53.

Thanks for he reply, I think I've done everything correctly but the log shows the following error ....


2013-08-23 10:07:49 DSC Alarm Initializing communication at address: envisalink:4025
2013-08-23 10:07:49 DSC Alarm Error Error opening socket: Could not open port socket://envisalink:4025: (8, 'nodename nor servname provided, or not known')
2013-08-23 10:07:49 DSC Alarm Plugin will attempt to re-initialize again in 3 minutes.

It's better to specify the IP address of the Envisalink rather than the name "envisalink". With some home routers/DHCP services the name will work, but not many. You'll have to find out what the IP address of the Envisalink is, and use that in the plugin configuration. What's probably happening here is that the Mac running Indigo can't resolve the IP address from "envisalink".

Try entering the IP address instead (if you don't know it, you can find it from the clients table on your router, usually), and ensure your router/DHCP server will always give the envisalink that IP. If you need help with that, feel free to PM me your router type and I can point you at where you'd do this, but it looks like the plugin can't connect to the card.

deadsquid wrote:It's better to specify the IP address of the Envisalink rather than the name "envisalink". With some home routers/DHCP services the name will work, but not many. You'll have to find out what the IP address of the Envisalink is, and use that in the plugin configuration. What's probably happening here is that the Mac running Indigo can't resolve the IP address from "envisalink".

Try entering the IP address instead (if you don't know it, you can find it from the clients table on your router, usually), and ensure your router/DHCP server will always give the envisalink that IP. If you need help with that, feel free to PM me your router type and I can point you at where you'd do this, but it looks like the plugin can't connect to the card.

Thanks for your help! I followed your advice and got the IP address for the EVL3 from my router (Airport Extreme) and used that in the plugin configuration, It's now working Another question, should I choose to use a static IP address for the EVL3?

I prefer using a static IP address for it so that it never changes. There's a couple ways to do it, including using the DHCP server to always set the same address for the E3's MAC address. You can use the AirPort Utility to do this. The other way is to set the IP to a static value via the E3's web interface. Remember to use an IP address that is outside the range of the DHCP pool to avoid any conflicts.

Sorry for the tardy reply, I had missed the notification.