EyezOn Forum

I guess. Bit academic though - doesn't matter if it's invalid 'cause it's short or invalid 'cause it's a bad checksum, I discard it in either case. What I'm trying to sort out is whether the envisalink itself has sent an invalid message or it's been corrupted while traversing the network. Which is ...

IIRC valid messages will always end in CRLF, and be a minimum of 5 data bytes -- 3 digit command/response code + 2 digit checksum.

So if you've got less than 5 data bytes and/or the message doesn't end in CRLF, you've got a short read and couldn't have something valid to checksum.

I wasn't able to find information about what is returned when the TPI is blocked by the envisalink firewall. I've seen my app report an invalid checksum - is this a sign that the request has been blocked? (I'm using a 2DS so I'm not able to check this myself). No, it just resets the TCP socket upon ...

Envisakit should be sticky and should be the core of all honeywell development: https://github.com/mklips0/envisakit Seems like this was probably the wrong topic. (There is another topic for Ademco, but this isn't really about documentation.) I think it would be helpful if there was a (sticky ...