EyezOn Forum

There seem to be some gaps in handling Zone Low Battery, which might be isolated to just the wireless keypad (WT5500).

When the keypad indicated it had low battery, the trouble LED went on, and this is picked up in most places. Verbose Trouble Status shows 0x40 but:

• Recent events on the portal doesn't have any log of when the trouble led went on/off.
• Recent events on the portal doesn't show the status that is available via the verbose trouble code which would indicate that the source of the trouble is zone low battery 0x40.
• There doesn't appear to be any way to get notified of this trouble condition. (The system hasn't turned on the Service Required bit, just the trouble LED.)
• The envisalink web page itself shows trouble, but doesn't breakout the other bits.

The portal status does show trouble next to partition 1, and if you hover you can see "Trouble Details: Device Low Battery", but AFAICT that's the only place it's available.

If trouble conditions occur, without triggering service required, I'd still like to see those show in in recent events and possibly be able to get alerts.

Right now the only way I can see what zone has a problem is to go to a physical keypad and view the system trouble to see it is Zone 29 where the wireless keypad is registered. Ideally I'd like to be able to see that from the envisalink, though I'm guessing the DSC panel isn't generating a zone fault message that the envisalink can pick up.

System details:
1832, 4.6cp
EVL 4, 102 firmware
WT5500 keypad, and TR5164 2-way transceiver.

Thanks for any help you can provide.

The Envisalink presents every event that the panel issues. If it isn't in your event log, then the panel never triggered an event. Most security panels will not issue events right away for certain events like low-bats or AC fail. Honeywell panels can take hours to report and AC failure.

What you see on the Eyezon details (status) page is what you see on a local keypad. What you see in the Recent Events, is what you see in the panel event log. In many ways the two are not related.

Sorry, I guess this wasn't very clear. Talking about a DSC panel, EVL-4.

The panel turned on the trouble LED. The Envisalink did catch that and generate the TPI codes for trouble LED on and off after the keypad batteries were replaced. The Eyez-on portal was aware of the Trouble since it displayed it in the web UI.

Enhancement Requests:

• The eyez-on portal's recent events / view full log doesn't log that the panel had decided there was trouble. I would like to see that trouble started/ended with date/time captured in the eyez-on portal log. The eyez-on portal did receive notification and parse the Verbose Trouble Bits (or equivalent) since it could be seen in the UI. However, It could be only be seen if you were logged into the portal at the right time and hovered the cursor in the right spot. There was no log, so as soon as the problem was cleared all traces of it went away. I consider the case that the panel declared trouble to be useful information that should be captured in the log.
• I would like the option to be notified if they panel indicates there is trouble, and the verbose trouble bits when available.

I should probably move this to the feature requests thread. I started a separate thread for this because I wanted to capture the details of what I've seen. I was also wondering if there is a DSC edge case here because it didn't generate any zone level TPI codes/notifications.

To me this seems particularly important since it is the WT5500 wireless keypad - I'd like to know if its battery is dying while the system is armed and I'm away.