cyberwave.data) to the cloud MQTT broker, forwarding selected channels in both directions.
Overview
When MQTT is disconnected, outbound messages are buffered to a persistent file-backed queue and drained in FIFO order on reconnect.
Quick start
Default topic mapping
Offline queue
When the MQTT connection drops:- Outbound messages are appended to segmented files under
CYBERWAVE_BRIDGE_QUEUE_DIR. - On reconnect, the queue is drained in FIFO order before resuming live forwarding.
- Queue size is bounded by
CYBERWAVE_BRIDGE_QUEUE_MAX_BYTES(default 50 MiB); oldest segments are evicted when the budget is exceeded.
Configuration
Transition compatibility
Existing direct MQTT paths (cw.mqtt.publish(...)) continue to work unchanged. The bridge is additive — channels published via both Zenoh and MQTT are handled idempotently on the cloud side.