EyezOn Forum

Maybe some can confirm this for me, but I think this is a limitation of the panel and not the IP1XXD board?

I had a wireless device that has a low battery, this puts the system in trouble status. The only way to determine the wireless zone # that has low battery would be from the keypad. From the *2 trouble, it will show the zone that is low bat, but from the system log (and what the IP1XXD logs), this does not show the zone that is low batt.

Does this make sense?

Yes you are correct that logging of low-bats are the responsibility of the panel, not the IPXXX, but I'm pretty sure the Power series panels log low-bats on zones. At least we support these type of events so if they are actually reported by the panel, it should be reported.

Do you see an event in your local event log (*6)?

There is no logged event in the local event log.

Ok, we can only report what is in the log, so this would be a question for DSC. It is a good one though. What panel do you have?

I've got a 864, but also testing with a 1832 with same results.

I think I'm going to answer my own question.

Local system log will log the event, but only after the timeout expires.

This can be found in section 377 of the programming. Default is 7 days, so once this elapses, then it will log locally (and to the ESP). Sething this to 0 days will be immediate updating of the logs.

2011-08-19 22:26:51 - Zone 1 Low Batt

Thanks for sharing Quatchi. I knew there had to be a way to report the event because I have seen it before in my own home, although it was a long time ago.