Indigo Domotics

I have an Evisalink 3. It has been working for years. After upgrading a CLIENT computer (not the indigo server) to Big Sur, I started receiving socket errors. I think the OS upgrade is a coincidence.

DSC Alarm Initializing communication at address: 192.168.4.101:4025
DSC Alarm Error Error opening socket: Could not open port socket://192.168.4.101:4025: timed out
DSC Alarm Plugin will attempt to re-initialize again in 3 minutes.

I can still use it with Eyez-On, and I can access it directly from the internal network, and I can ping to it. The exact port, however, is inaccessible.

Set up:

1. Indigo server running on an old Mac mini
2. Evisalink 3
3. Apple AirPort Extreme. Base Station
4. Client indigo on Big Sur

It seems I had this problem as well at some point, just don't remember what I did to fix it. One think you can try, if you haven't already done so, is to power down your alarm system, but AC and battery for a minute or two in hopes of resetting the interface.

The other more laborious thing is to disable comms to your existing alarm device, and try to create a new new one just to see if something has become corrupted in your existing device in Indigo. Doubt this will have much effect but might be worth a try

Check in your "eyez-on" account. they have firmware updates for the modules, I just updated mine today.. Mind you I have a 4 not a 3..

Might be with a shot, if there is an update it will say, UPDATE NOW beside the firmware version.

Is is possible that following the upgrade a previous install of the plugin (maybe an earlier instance of Indigo) has been restarted on that client machine. I had a similar issue when I migrated from Vera to Indigo as the Envisalink will only allow one single connection.

Turns out, an installer knocked out an ethernet cable in the attic. We have a DataRemote that kicked in (backup internet) and I hadn't noticed. So everything was online, but on a different router.