alarmdecoder.com

Greetings. Using a library that purports to parse the ad2usb message stream into an object. (https://github.com/jlong23/node-red-node-ademco)

Long story short, when it parses the first section of a message (splitting on ","), it tries to read bit number 15 as indicating a ZONE fault... I see in the documentation that 15 is simply "system issue". Is this accurate?

If it IS, then why is bit 15 0 on the following message coming from my Ademco Vista 10SE?

[00000001000000000A--],005,[f70000008005000008000000000000],"FAULT 05 ZONE 05 "

Ideas?

Bit 15? For zone data? I don't think so... zone data is the numeric code section - if zone 15 for example, it would show 015

Please look at our alarmdecoder python library for example on how this is done. There are also built-in zone tracking algorithms which are necessary to track faults and restores properly on ademco panels.

No, I know that part, it isn't parsing it to indicate WHICH zone is faulted, its using bit 15 to determine THAT ANY zone has faulted (boolean, true false).

I believe in the python lib, this is "check_zone".

You're right - it could potentially be a bug in the firmware, if you could email your findings to ad2usb@support.nutech.com that would be great.

Though I don't know if it is potentially SE related or not - those things honestly are a real PITA.

Will do. Yeah, it looks like either a bug in how the raw message is parsed, or my old ADT Ademco Vista 10SE is doing something weird... if it helps, I DID have relays configured (turned that off and reset the setup on the AD2PI as part of my testing of this). My thought was maybe that was swallowing the actual zone fault or something.

Ill send an email now. Thanks!

Sorry to beat a dead horse here, but does someone monitor that email or the contact form? I haven't gotten any response to my emails in almost a week, so I just wanted to make sure this doesn't get lost.

If you got an autoreply with a ticket number then you know it has gotten through to the support system

Ah, Ok, found that ticket message in my spam folder. Ill continue to wait on a response then.

Yeah, sorry to keep you waiting - the engineer responsible for those kind of firmware questions has not been available this week. Software or protocol related? I can help - but innerworkings of the firmware and potential panel compatibility issues is not me, unfortunately.

OK, well you should have gotten a reply from the engineer with further steps and ideas - we should continue this conversation through the email ticket chain now.