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

..

design

net: re-address hub network 10.60.1.0/24 -> 192.168.8.0/24

2026-06-05 07:47:57 -04:00

plans

CUB-196: add accessibility and edge case fixes for CameraCard

2026-05-21 11:59:40 +00:00

CONTEXT.md

net: re-address hub network 10.60.1.0/24 -> 192.168.8.0/24

2026-06-05 07:47:57 -04:00

MQTT_CONTRACT.md

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

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