Syslog messages and Vista20 Event Logs

[HWL1223]

I am a new user of the EVL4 and am currently very impressed with it. Thanks!
I have a Vista panel monitored by an alarm company via LTE so I don't want to break anything (yet) with that setup. Its a simple single partition 8 zone wired setup. My inquiry concerns the messages I see on my syslog report.

I DLed KiwiFree and it is running properly. However, both on Kiwi and on my EyezOn panel I only see Zone openings and closings and reboot info. I have NOT yet triggered an alarm, but why do I not see when I set ARM and DISARM or do Bypasses? The info displayed is labeled Info and Warning.

The Vista manual shows Item 90 = Event Log Enables. Would this be the area to change (#15), and if so, will that mess up the info required by the monitoring company?

Thank you
HWL

[guinness]

The syslog feature isn't particularly well documented, but for the Vista you should get zone openings/closings, shutdown and contact id events.

For contact id events the 10 digit code is broken down as follows:

Code: Select all

           event type
           │event code
           ││  partition number
           ││  │ zone/user number
           ││  │ │  checksum digit
           │├─┐├┐├─┐│
CID Event: 1131010080

The event codes are grouped into the following categories:

Code: Select all

1XX ALARMS
2XX SUPERVISORY
3XX TROUBLES
4XX OPEN/CLOSE REMOTE ACCESS
5XX BYPASSES/DISABLES
6XX TEST/MISC

The Contact ID Codes were designed for reporting to the central station. What are you trying to achieve, local logging or reporting?

[HWL1223]

I think I am trying to see local logging in Kiwi Syslog. That said, I have not triggered any alarms, but have set and un-set alarms with no log info reported. Also done commands with no logging shown.
As I said I do see zone openings and closings. All the above would be nice to see.

example:
03-27-2022 21:37:57 Local0.Info ENVISALINK[001C2A035E]: Zone Open: 5

Thanks

[guinness]

If you have the installer code, you'll probably have to change field *90 (Event Log Enables) to include Open/Close. Bear in mind that'll increase reporting to your existing alarm company which may not be desirable. You could also look at TPI Documentation as an alternate way to achieve what you ultimately want to do (if not just passive logging).

[HWL1223]

I changed field 90 to 15 and confirmed it on the panel (from 03) but my syslog does not show any new fields/messages, meaning it just shows what is always has; reboots and zone opens and closed.
Ideas? Thanks

- also seems the original install company never set the date and time! doh!

ALSO - I now triggered test alarms and received the following in my syslog:
03-28-2022 14:54:06 Local0.Notice ENVISALINK[001C2A035E]: CID Event: 1406010020
03-28-2022 14:53:52 Local0.Warning ENVISALINK[001C2A035E]: Alarm Zone: 001
03-28-2022 14:53:51 Local0.Notice ENVISALINK[001C2A035E]: CID Event: 1134010010
03-28-2022 14:53:51 Local0.Info ENVISALINK[001C2A035E]: Zone Open: 1
03-28-2022 14:53:35 Local0.Notice ENVISALINK[001C2A035E]: CID Event: 1459010020

I can somewhat decipher the Event #s but at least I see an alarm Event/report in my syslog. Interestingly, the email I get from EyezON only shows the alarm cancelled. (nor do my monitoring company's logs have numbers similar to either the syslog or Vista manual).

[guinness]

The three CID events, in chronological order are close (arm) by user 2, alarm in zone 1 and abort (cancel) by user 2.

[HWL1223]

guinness - thanks for all your help!