search

Tertiush / ParadoxIP150v2

Python-based IP150 'middle-ware' that uses the IP module's software port for monitoring and control of the alarm via an MQTT Broker.
Eclipse Public License 1.0
73 stars 35 forks source link

Heart beat event #32

Open psyciknz opened 6 years ago

psyciknz commented 6 years ago

I've added a reply to the heartbeat message (keepalive). 2018-05-31 08:15:23,945 DEBUG 64-> 0xaa 0x25 0x0 0x4 0x8 0x0 0x0 0x14 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x50 0x0 0x80 0x4 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xd4 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe The important bits of this are the 50 0 80 04 - which from the SPxxxx protocol document is supposed to be panel status message 04.

But the reply that all the status messages gets is an 70 0 10 - which I think is an error, or a panel disconnect....but it's recording event to it's fine.

2018-05-31 08:15:24,200 DEBUG 53<- 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x70 0x0 0x10 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0 x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x80

I've wiresharked this, and I can't see anything wrong with our keepalive call but the response is wrong. I'd like to get this sorted so I can understand the arm/disarm commands. I think I've got a fairly good handle on the protocol now.

@Tertiush