MQTT Reference

Every MQTT topic published by the receiver, message processor, archive processor, and rule notifications, plus the map service's UDP feed (message-processor → map) and WebSocket API (map → browser) — rendered interactively from specs/asyncapi.yaml.

Home Assistant

When MQTT is configured, every component publishes Home Assistant autodiscovery payloads on connect — each message processor, receiver, archive processor, and data runner appears as a device in Home Assistant with sensor entities for its key metrics. Rule notifications (SkyFollower/rule/{identifier}) carry the flight's current state as JSON and can be consumed by Home Assistant automations directly — see Rule notifications for the payload shape, its omit-when-empty fields, and the delta table for porting automations written against the legacy payload.

RabbitMQ / AMQP

This page covers MQTT, UDP, and WebSocket. The internal RabbitMQ exchanges and queues that move messages between the receiver, message processor(s), and archive processor — skyfollower-adsb, skyfollower-adsb-unroutable, skyfollower-archive, and each message processor's own skyfollower-message-processor-{id} queue — are documented separately in specs/asyncapi-amqp.yaml, kept as its own AsyncAPI document rather than a second server here.