Application Event protocol (ID 1)

Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 (opens new window).

Overview

Application Event messages MAY be used when an Event occurs on the End Device. Examples are "Temperature is 22 degrees celcius" or "Presense detected". The message format is specific to the End Device and there are no requirements for the message format. , it MAY be binary and it MAY contain an array of messages like 4 bytes temperature, 4 bytes humidity and 4 bytes air-pressure. This allows for efficient communication as the Network server knows the format and how to decode it.

Predetermined data format

As the Network Server knows the message format of the End Devices, there is no need to create a message format that describes itself. The only requirement is that the Network Server knows what Device Types and their respective Data Types it must decode.

Event Message format

Event Message format:

Event specific message 1-58 bytes

Example packet

Full packet:

Pre. 4 bytes	Sync 4 bytes	Len 1 byte	FDAddr 1 byte	FSAddr 1 byte	FHdr 1 byte	THdr 1 byte	Event 1-58 bytes	CRC 2 bytes

Encryption covers the transport layer and the application layer, meaning THdr, TSeq and the Event bytes (the message).