34 lines (23 loc) · 797 Bytes

Runtime Behavior

This document describes how the system behaves while running.

Normal Operation

Devices publish telemetry periodically
Heartbeats update device liveness
Core processes messages asynchronously
Dashboards reflect near-real-time state

Device Disconnects

Missing heartbeats mark a device as degraded
No retries from backend toward devices
Device state is preserved until timeout

MQTT Broker Restart

Devices reconnect automatically
Core resubscribes on reconnect
No manual intervention required

Raspberry Pi Reboot

systemd restarts services
Core rebuilds in-memory state from persisted data
Devices reconnect naturally

Data Flow Guarantees

Telemetry is best-effort
Events are prioritized
Health state is eventually consistent