3: Event
🧪 Alpha
New message type for server side events, subject to alterations
Used to indicate that an event has occurred. Events may be used to notify of state changes, errors, warnings, or other significant occurrences. Initially this will only be used for server side events, such as device connected, disconnected, RTK errors etc. Probable header fields: - Client ID will indicate the device the event relates to. - Status will indicate if the event is an error or OK. - Received Time may be added by cloud systems to indicate when the event was generated
Payload
| Field | Name | Description | Type | Unit |
|---|---|---|---|---|
| 1 | Service | Service the event relates to, e.g., "CHASM" | ascii | |
| 2 | System | Sub system the event relates to, e.g., "UDP_IN" | ascii | |
| 3 | Code | Code identifying the event, e.g., "DEVICE_CONNECTED" | ascii | |
| 4 | Text Data | Text for the event (optional). Additional context... | ascii | |
| 5 | Integer | Integer data for the event (optional). Additional context... | int32 |
Code
For convenience, the following constants can be used to reference this message type.