ANNOUNCE: EVL4EZ Syslog Client

Information and support for EnvisaLink modules.

Moderators: EyezOnRich, GrandWizard

Posts: 6
Joined: Sat Oct 21, 2017 11:17 am

Re: ANNOUNCE: EVL4EZ Syslog Client

Postby Ltek » Sun Oct 22, 2017 10:45 am

GrandWizard wrote:No, the EVL3 is retired. While it is will always be supported, only critical updates are being issued for the EVl3 firmware.

Are the devices differ so much it can would be difficult to add to the EVL3?
It's unfortunate if it would be easy to add while still choosing not to. Adding to EVL3 shows loyalty to the customer, even though it's not critical it is a nice feature for home automation integration.

Posts: 41
Joined: Mon Dec 21, 2015 6:24 pm

Re: ANNOUNCE: EVL4EZ Syslog Client

Postby rct » Wed Oct 25, 2017 11:15 am

A helpful enhancement would be to syslog loss of connectivity to the envisalerts service and restoral.

(Last night I had an internet outage which was logged by the envisalerts service as you would expect. However nothing was syslogged with firmware 01.01.114. I'd also love to see TPI codes for loss of envisalerts/internet connectivity that my app can use.)

Posts: 6
Joined: Sat Oct 21, 2017 11:17 am

Re: ANNOUNCE: EVL4EZ Syslog Client

Postby Ltek » Fri Dec 01, 2017 4:00 pm

Does Syslog report all zone activity (motion, door/window/etc) both when armed and disarmed?

Posts: 1764
Joined: Tue Nov 16, 2010 4:08 pm

Re: ANNOUNCE: EVL4EZ Syslog Client

Postby GrandWizard » Sun Dec 10, 2017 1:47 pm

Yes for DSC users. Honeywell panels don't report zone activity while armed so no for those users.

Posts: 1
Joined: Tue Jan 30, 2018 11:00 am

Re: ANNOUNCE: EVL4EZ Syslog Client

Postby joyn » Wed Jan 31, 2018 1:22 pm

Regarding "Honeywell Vista 20P does not report zone activities when armed", this does not seem to be true to me. I just recently switched to Eyezon (EnvisAlert, and EnvisAlarm CS monitoring). I was with Rogers SHM before the switch. It is the same Vista 20P control panel. It was able to report entry door open when armed (either stay or away) - when you open the door, then close the door, then disarm (or you disarm then close door. it was reporting three entries (either you call the first an activity and the second an event - different names by different company). But now with Eyezon, it only reports as one event (opening by user xxx). It appears to me this is not a control panel reporting issue but rather how Eyezon envisAlert is programed/configured (at the server side) to send alerts to the client - maybe by purpose of reducing bandwidth? As in such scenario, the panel would send the contactID message for the zone/door open, then a second message for disarming to the server (and monitoring station if signed up with CS monitoring). Combined the two into one alert is omitting the information about from which zone/door is opened and then closed.

If it's bandwidth issue, then I suggest maybe to reduce or eliminate the reporting of zone activities for those interior Motions zones when the system is disarmed. You don't care (actually I don't want) zone activities of motion sensors when the system is disarmed. It will save bandwidth so more events of interest can be sent to client more frequently (the 5 minute gap is too long to follow a zone or between events alerts).

Return to “EnvisaLink ( IP100D, IP170D, 2DS, 3, 4)”

Who is online

Users browsing this forum: No registered users and 12 guests