EyezOn Forum

Hello, I was looking through the security log and noticed a couple of gaps in activity that lasted for several days (e.g. from 1/23/16 to 1/31/16 and also from 12/19/15 until 1/08/16). I did not receive any notifications of lapse in network supervision around those times and in looking through the log, I do not see any similar gaps before that time, except when I know we were away from the property. I know were were home during these two gaps and that there should have been activity recorded.
What prompted me to check the log was that I received an alert this morning with the message "Maximum Event Limit Reached - Slow Down." This alert was received at 5:15AM when the alarm was not armed and we were sleeping. Prior to that there were no events recorded in the log for 8 days.
Has anyone else seen this type of behavior?

I have a DSC PC1832 panel with Envisalink 3 and have had it working without issues for about 2 years. I appreciate any input to solve this mystery.

Thanks,

Rafael

Your module was most likely offline. The Envisalink has a finite event buffer so once that is full you can't buffer any more events. The Maximum rate limit message means your panel probably "dumped" all of its buffered messages at once when your network service was restored. There is a maximum rate limit of 75 events within a 10 minute period (450 events per hour).

Thanks!

Not sure why I never got a "no Network supervision" alert. I checked that it is enabled, and I have received them in the past.

Eyez-Support explained that the module wasn’t offline during the gap period, it had 100% return packet loss. He also said if I had logged into my account in that time I would has seen a big warning about this. Most of the time this indicates that another device on the network has the same IP address as another device but it can also turn up with faulty wireless bridges. I have a wireless bridge connected to the envisalink and do remember having to restart my wifi router during that time, so there may have been a duplicate IP situation created. Anyway, the issue is now resolved. Thanks.