alarmdecoder.com

We are having a problem where it is impossible to clear and re-arm the the alarm from the keypad after the alarm is tripped.

We can successfully clear and re-arm the system only if we use the web interface through the AD2USB/Vera Lite. System is new Honeywell P15. Once system is cleared in this way, physical keypad will work properly.

Any ideas on a fix?

That's an odd one.

Can you confirm that the AlarmDecoder and physical keypad are at different keypad addresses? It's possible the Vera is attempting to send commands (probably a *) in order to retrieve faulted zones and if they're at the same address there's a definite possibility of keypress collisions if they're sharing the same address on the bus.

It sounds like a driver issue with Vera. Can you send logs from the Vera system? I suspect the Vera is telling the AD2* to send '*' or some other message to the panel too fast and prevents a keypad from entering all the digits to disarm before interrupted. I do not think this is a Ad2* specific issue it is just doing as it is told by the driver.

Re
Sean M

I removed AD2USB from the system and the keypad cleared and I was able to arm the system manually. At least now we have the alarm armed at this property. Is there a way I can see what device is set to what address on the P15 via the keypad? There are two keypads and the AD2USB on this system. The alarm tech assured me that he assigned different addresses to each but he has been unreliable in the past and I want double check myself.

Thanks,


James

Pressing 1 and 3 at the same time on a keypad will report the address it is assigned to. Some keypads need to be powered down and this then must be done within 60 seconds of adding power back to the keypad but most just report the address. Some keypads that have a built in RF radio this results in a different screen and I dont recall the exact way to get that address.

Re
Sean M

Thank you. How do I tell what address the AD2USB is on?

You can enter configuration mode by pressing ! in a telnet or terminal session with the Ad2* and press enter through all the prompts or you can press C to have it dump the config line. You can also see this in the AlarmDecoder App by going into the configuration screens. By default they are all set to 18.

Re
Sean M

I am having the same problem. I just had the alarm company here for several hours trying to figure it out. There belief is that there a bus conflict with the AD2USB and the expander module on my Honeywell Vista system. Is there a way to assign the AD2USB to bus 08? Port 18 works fine and I can control the system until there is a trip, then my panel locks.

Easy to fix just need the address and device info to find the conflict


Please send the current configuration of the ad2 by pressing C in putty or a terminal or out of the keypad app gui log it will show up on startup

Then tell us about your panel expander(s) and keypads and the addresses of them. pictures of the panel help too.

Re
Sean m