Events
The reader publishes three events on its own. None carries a requestId or a response, and none names its own kind: recognize each by the members it carries.
| Event | Arrives on | QoS | Recognize it by |
|---|---|---|---|
mqttConnEVT | The endpoint's connection-state topic, publishTopics[2] | 0 | connectionState |
heartBeatEVT | The endpoint's event topic, publishTopics[1] | 0 | eventName: "heartbeat" |
alerts | The endpoint's event topic, publishTopics[1] | 1 | type, id, state and priority |
heartBeatEVT and alerts are enabled with config_events. Whether mqttConnEVT is retained is not settled; the others are not retained. Tag data, the fourth event, is under Telemetry.
In This Section
MQTT Connectivity
The per-endpoint CONNECTED and DISCONNECTED signal.
Device Health
The periodic liveness signal — uptime, event sequence, inventory status, battery.
Alerts
The alert envelope (type, state, id, priority) and the six alertDetails branches.