Device Health

The reader publishes heartBeatEVT at the configured interval (at most 65,535 seconds) while the heartbeat is enabled with config_events; a reboot applies the setting. Monitoring can rely on it as its primary liveness signal: when heartBeatEVT stops arriving, the reader, its session, or the path to your application needs attention. It is published at QoS 0, so the MQTT layer does not resend one lost in transit; choose how many missed intervals your application treats as an outage. When enabled, it carries inventory and battery status.

See Monitor Reader Health and Battery.

In This Section

💓

heartBeatEVT

MQTT reference for the heartBeatEVT event: the periodic liveness signal — uptime.