Help w/ Vista 20p and EVL3 not reporting zone activity

[fondy]

I have a Vista 20p and EVL3. I thought the system was working fine since when in Unarmed mode the Envisalink "app" showed activity on all my zones when they were triggered. However today when I decided to put the system in test mode and Armed Stay, I discovered that zones that are being triggered are not showing any activity on the app. This includes zones set as Type 03 Perimeter, so they should not be ignored in Stay mode. I do receive an Event Alert that the zone was tripped (I set Burglar Dial delay to 0), but like I said there is no report under Zone Activity. Basically the EVL3 is mainly only working for me in Unarmed mode right now. I have it configured per the instructions from Eyezon for Honeywell 20p panels. Thank you for your help.

[GrandWizard]

This was just two threads down from your posting...

http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=1251

[fondy]

Grandwizard,
Yes that was me who started the other thread. Thank you for your reply to that one. In that thread I was noticing the EVL would not report the status of Interior zones in Stay mode. However now I am realizing the EVL3 does not report the status in Zone Activity of ANY zone type when the system is armed. In fact in Armed mode the only things it reports are alarm events that get sent after the burglar dial delay and alarm restores. For it to report zone activity the system has to be disarmed. This is a serious drawback of the EVL when used with Vista panels and one I hope Eyezon will address. It's not as if the zones are being bypassed as they are in Stay mode. The keypad is showing the zone faults but the EVL is not reporting it. I thought my situation was unique but since starting this thread I have found other user posts regarding the same issue.

It is nice to be able to use the EVL to arm/disarm my system and see its arming status as well as be notified of any alarm events. But not knowing Zone Activity when the system is armed is a big loss of functionality IMHO.

[fondy]

Here is a link to another thread on this forum where Vista 20P users were experiencing the same problems as me, namely that Zone Activity is only reported when the system is Unarmed:

http://forum.eyez-on.com/FORUM/viewtopi ... 170e7037d6

This was way back in March 2013 of last year.

[GrandWizard]

And here is a link to the FAQ that explains the situation.

http://forum.eyez-on.com/FORUM/viewtopic.php?f=11&t=463

[dcuste]

I also have a 20P and the workaround that worked for me was to put zones I wanted to monitor in partition 2 and just never arm partition 2. This workaround worked great for over a year and then a little over a month ago it stopped working. It appears now that it will only work as long as I assign one of my keypads to partition 2. I didn't make any changes at my end. It is kind of weird because even without a partition 2 keypad, envisalink will still allow arm and disarm operations and report when partition 2 is read and not ready. Just the zone faults are not being reported anymore unless a keypad is assigned to partition 2. Very strange.

I would be real interested if somebody else with a 20P can verify this same issue.

[GrandWizard]

Pull a support ticket indicating your situation. You may need updated firmware.

[dcuste]

I did. It is ticket 15242.

[dcuste]

EyezOn loaded beta firmware into my EVL3 this morning and my alert problem went away. So my suggestion to anybody with a Vista system that wants to monitor a zone while the system is armed, may want to consider getting the beta firmware and put the monitor only zone in an unarmed partition 2.

[DonsHobby]

EyezOn loaded beta firmware into my EVL3 this morning and my alert problem went away. So my suggestion to anybody with a Vista system that wants to monitor a zone while the system is armed, may want to consider getting the beta firmware and put the monitor only zone in an unarmed partition 2.

Hi Dcuste. How did you configure your EVL-3 for partition 2 with NO keypad? I can't seem to get any reporting from my EVL-3 with no keypad (I just have it set up with the single keypad configured as partition 1).