EVL3 notifications

[DonsHobby]

Hi all. I've had an EVL3 for a long time. I used to get alerts from Eyezon on my phone but nothing is working now. Here is what I did so far:
- I deleted all "contacts" and added a new one. The only choice I have (on Rogers) is email I think. So I did that.
- I have that contact set up to receive alerts for arms/disarms, etc.
- After arming/disarming, I'm not getting any notifications.
- The EVL3 is on " 01.12.203A" firmware. So almost up to date.
- When I log into the Eyezon portal, I don't see any arm/disarm activity. BUT I do see events for zones (only if disarmed of course).

So I guess my questions are:
1) First off, as a Rogers cell phone user, is email notifications the ONLY way to get alerts on my phone? I thought I could still get PUSH notifications through the app?? Really confused here on this part. I've read the docs and I'm really NOT sure how to get PUSH notifications through the app on the phone.
2) Should I be seeing arm/disarm events in the eyezon portal?
3) Why is my new "Contact" not getting any email notifications? I had set up my brothers system and this was working for him (he has an EVL4 on apparently version 136. So way out of date. But at least it works.

On my brothers EVl4 with 136, I do indeed see the arm/disarm events in the log. But not on my EVL3 system.

Anyhow, not sure where to go at this point. Anyone? @GrandWizard?

EDIT: BTW my panel is a Vista20. I can arm/disarm from the app and the eyezon portal no problem. Just no notifications.

[GrandWizard]

Hi, you should submit a tech support request from your Eyezon portal so a tech can give you a definitive answer as to what is wrong with your system. But for the the benefit of others....

1) You get PUSH notifcations just by installing the app on your phone. Once done you will see a new contact on your system for the phone.
2) On a VISTA panel you need to program the panel to send these alerts. If you don't see them in the log, then the panel is not sending them. If you had them in the past then someone has changed your programming.
3) See #2

[DonsHobby]

Thanks.
- Alright I'll create a ticket.
- In general, nothing has changed on my system. I'm the only one who programs it.
- When I reinstalled the app on my phone, it did NOT create a user.
- The ONE change in the past year is a new router. However, from the eyezon portal I am able to see my system and arm/disarm it. So does that indicate that everything is all well with the router settings? Hmmm. Maybe it's something to do with that.

EDIT: WAIT. Now I am seeing the "new user" that was created from the app install. This is getting weird. It wasn't there awhile ago. But still no push notifications for arm/disarm (or events in the log either)

[GrandWizard]

Hi, just to close the loop for other users, this customer came into tech support and we could look at his account. He hasn't programmed his panel to send any opening/closing reports (*65 and *66) so this is why there are no alerts generated. Honeywell customers need to complete all of the programming steps on pages 9 and 10 of the Honeywell installation manual.

[DonsHobby]

Actually that's not true. Using this document here (https://www.eyez-on.com/EZMAIN/EyezonEn ... nGuide.pdf) I went completely through the programming for the Vista 20P from steps 3 to 23 and redid it (the Honeywell system does NOT show the current programming, so all you can do is redo it). I programmed them all to exactly what the doc said.

Still NO events logged for Arm/Disarm OR alarms for my EVL3 on the eyezon portal under activity.

The EVL3 is properly pushing data out the TPI data and my SmartThings HA driver IS receiving the Arm/Disarm/Alarm events no problem.

But for whatever reason, the Eyezon is not reporting ANY of those Arm/Disarm events to it's server.

Zone changes are showing in the Eyezon portal under activity. As are TPI Session Connect/Disconnect events. And of course I can arm/disarm from inside the Eyezon website and app.

One positive note, the TPI session Connect/Disconnect events are actually getting PUSHed to the app. So at least that part is resolved.

But that's it. I'm at a loss. I'm not sure where to go from here to get the actual important events to log. I've also powered down the panel/EVL3 several times and moved it off my VLAN as well. Nothing helped.

Any suggestions?

[DonsHobby]

@GrandWizard or anyone???. We are running out of options to fix this. Not sure if you are the same as the support team I'm speaking with, but I thought I'd ask you as well. It looks like everything is programmed correctly in the 20P panel. But for whatever reason, still no events for arm/disarm or any alarm events at all. I set a report code for Test mode which is supposed to report on exit. Still nothing.

From a Honeywell Alarm panel user perspective, it all seems to work well. I can arm/disarm. The alarm goes off properly, etc.

From a EVL3 user perspective, all seems to be ALMOST working. The TPI is working properly. I can arm/disarm from the app and eyezon portal. The zone reporting works (when unarmed as expected). Apparently "The alarm panel is also "pinging" the Envisalink every 30 seconds so it knows it is installed". I enabled TPI session alerts and those work as well. So we know from that alone that the end to end reporting should be working (I assume an actual alarm report from the EVL3 would use the same protocol). So it indeed seems that either the panel is either not passing alarm codes to the EVL3 OR the EVL3 is ignoring them for some reason.

Support is suggesting replacing with an EVL4 or wiping out the panel to defaults/reprogram.

There must be something we are missing. Do you have any suggestions? I'm deep into this now and have re-familiarized myself with the crappy 70's Vista 20p programming, so this would be a great time to try to get to the bottom of this.

If I may ask, on the EVL3 side, what exactly is the protocol for you to receive the Alarm Code? Like if the user ARMS the panel, how is that relayed to the EVL3? Perhaps if I know this, I could debug further (loose wire or something??)

Thanks for your help so far.