Joshua King 7929d1d969 registration: self-assigned camera IDs (Option B) + tolerate clockless status ...

Auto-registration never completed: the firmware announced on the wrong
topic, the hub never replied, and an unregistered node couldn't receive a
reply anyway. Switch to self-assigned IDs:

firmware (esp32-mqtt-bridge.cpp):
- camera_id defaults to the device id (clientID, e.g. rig-86d978)
- always subscribe to <id>/command; announce on the contract topic
  remoterig/cameras/<id>/announce (was the unmatched announce-<id> form)
- drop the bogus numeric timestamp from status (node has no clock)

hub (subscriber.go):
- handleAnnounce registers new cameras under the node's self-assigned id
  (no cam-NNN, no registered reply)
- handleStatus tolerates an empty/invalid timestamp and stamps server-side
  (previously rejected the status outright)

docs/MQTT_CONTRACT.md updated to match.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-05 12:14:00 -04:00

..

api

fix: harden camera API endpoints (CUB-234)

2026-05-23 08:50:21 -04:00

auth

CUB-182: Chi router setup with auth middleware and graceful shutdown

2026-05-18 17:47:06 -04:00

db

Merge branch 'dev' into agent/dex/CUB-239-hub-dedup-replay

2026-05-28 06:59:51 -04:00

events

feat: harden SSE endpoint with typed events and Last-Event-ID

2026-05-21 21:18:24 +00:00

mqtt

registration: self-assigned camera IDs (Option B) + tolerate clockless status

2026-06-05 12:14:00 -04:00