EyezOn Forum

All

I know there is the link to the Honeywell Programming (https://www.eyez-on.com/EZMAIN/EyezonEn ... .pdf#page9) but I had a question before I start doing this with an EVL4. Specifically, already have totaljconnect / alarmnet monitoring on the panel. Can I just follow the EyezOn programming and that will retain the current configuration too OR does it wipe out ? The reason I ask is that I want (at least for now) dual monitoring (alarm net + other). Will be using this with HA as well.

For reference this is a VISTA-21IP VISTA panel

Thanks all for the advice.

The answer is yes if you don't use your onboard IP communicator for TC. If that is the case then no, as the Envisalink and the onboard Ethernet cannot be active at the same time. The panel cannot support both the onboard Ethernet, as well as an ECP connected communicator like the Envisalink.

Thanks for the reply. My follow up question is if I then disconnect the ethernet cable from Envisalink will TC resume and vice versa OR in configuring for Envizalink does it wipe out the TC programming ? My original understanding was that both could co-exist based on another post I subsequently saw but it appears you're stating thats not the case. I thought that was the purpose of IP/GSM/LRR Shadowing, no ?

Post I came across was - viewtopic.php?p=14051&sid=fa97f8877b1b1 ... 1ab#p14051

No programming is lost, but you can't use the onboard Ethernet on the 21IP and the Envisalink at the same time.

If you were using the external ECP Honeywell IP communicator for TC, then you could use shadowing, but the 21IP is different in that it want allow and external comminicator and the onboard at the same time. Its not a conflict, it juts want try and talk to an external communicator on the ECP bus if the onboard is in use.

GrandWizard wrote: ↑Wed Oct 23, 2024 11:41 am No programming is lost, but you can't use the onboard Ethernet on the 21IP and the Envisalink at the same time.

If you were using the external ECP Honeywell IP communicator for TC, then you could use shadowing, but the 21IP is different in that it want allow and external comminicator and the onboard at the same time. Its not a conflict, it juts want try and talk to an external communicator on the ECP bus if the onboard is in use.

Thanks for your response. A quick follow up. While this makes total sense, what I'm seeing, appears to be different. Specifically, if I have both ethernet cables (onboard + EVL4) plugged in and live at the same time, I can login to TC and to Envisalinnk (web GUI local, wan gui, even HA) and see both current status and updates when I make them. Wouldn't this signify that both are working at the same time ?

Thanks

The Envisalink is actually two devices in one. It is both a keypad, and an external communicator. While the keypad function will still work if you have the onboard communicator enabled, the communicator portion will not work as the panel will not send any events to the ECP communcicator if the onboard communicator is enabled. Without events, you will not get any notifications of alarms etc.

GrandWizard wrote: ↑Mon Oct 28, 2024 8:21 am The Envisalink is actually two devices in one. It is both a keypad, and an external communicator. While the keypad function will still work if you have the onboard communicator enabled, the communicator portion will not work as the panel will not send any events to the ECP communcicator if the onboard communicator is enabled. Without events, you will not get any notifications of alarms etc.

Ok and to clarify a couple of things.

1 - With both plugged into ethernet, only 1 will communicate to monitoring centers and the onboard Vista would be that one ?
2 - To resolve all I do is remove one ethernet cable and whatever 1 is left will be the live one to the monitoring center ? In other words if onboard = TC and Envisalink = Their own monitoring, I unplug onboard and Envisalink center will get alarm ?

Thanks

You're close. There is a jumper on the 21IP near the Ethernet jack that selects between the onboard IP communicator and one that's connected to the ECP bus. If the jumper is ON, the signals go to the onboard Ethernet communicator. If the jumpter is OFF, it disables the onboard communicator and signals are sent via the ECP bus instead.