Just got the Invisalink3 and I love this product. I was thinking that connecting our DSC panel to my network was going to be a headache, but your product made it easy peasy!
I am a network security professional, and I run a syslog server and a SIEM in my home, to monitor and alert on threats. I am in the process of developing my own system that more or less does the same thing for physical security. I would like to request a local syslog sender added to the EVL3 module, for sending logs in real-time on the local LAN. I don't know if others are used to this, or use this with anything else, but I think it would go along way with those who are trouble shooting, and help me correlate physical security information with other data sources.
I know its a long shot, but I figured I would ask.
I suspect you, myself, and probably 5 other owners know what you're talking about but I do understand why that would be nifty.
If it wasn't for the large reporting set (mainly for DSC panels) that the Envisalink can handle, it might even be doable within the current memory confines of the Envisalink 2DS/3. Unfortunately Syslog uses all human readable text for logging and that takes up whacks of valuable code-space. If we did add such a feature it would have to be limited to things like "SYSTEM ARMED". I'm not sure if that's useful to anybody.
Anyhow, the Envisalink has a local API (TPI) that works as a TCP server instead of like a syslog client. I'm pretty sure you could write a PERL script that connected to the TPI and dropped events into the syslogd. It might be a nice afternoon project.
