# Network Event protocol (ID 2)
Network Event messages are defined by the protocol and MAY be extended by the use of proprietary events. The event ID is set in the Event of the frame and the payload is specific to the event.
| Event 1 byte | Event specific payload 0-57 bytes |
|---|
The following table list the Events that and End Device MAY support:
| Event ID | Event | Description |
|---|---|---|
| 0x1 | Device Status | TBD |
| 0xA0 - 0xEF | Proprietary commands | |
| 0xF0 - 0xFF | Reserved |
# Device Status (0x01)
The Device Status frame consists of Battery level and firmware version. There are two reasons for sending this frame:
- If the ED sends unreliable messages (un-ack'd) then the only way for the GW to send messages to the ED is on the reply-ack of this Device Status message.
- If the ED does not get a reply (ACK) from the GW after 3 successive attempts, then it MUST re-join the network.
This frame SHOULD be sent at least once per day but depending on the application it MAY be sent more often.
Frame structure:
| EventID 1 byte | Battery level 1 byte | FW major 1 byte | FW minor 1 byte | FW patch 1 byte |
|---|
The battery level is one byte describing the level in percent from 0-100%.