Kpa-clawbot 95afaf2f0d fix(go): add nested packet field to WS broadcast, fixes #162 ...

The frontend packets.js filters WS messages with m.data?.packet and
extracts m.data.packet for live rendering. Node's server.js includes
a packet sub-object (packet: fullPacket) in the broadcast data, but
Go's IngestNewFromDB built the data flat without a nested packet field.

This caused the Go staging packets page to never live-update via WS
even though messages were being sent — they were silently filtered out
by packets.js.

Fix: build the packet fields map separately, then create the broadcast
map with both top-level fields (for live.js) and nested packet (for
packets.js). Also fixes the fallback DB-direct poller path.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

2026-03-27 13:31:37 -07:00

..

ingestor

fix: Go ingestor normalize mqtt:// to tcp:// and mqtts:// to ssl:// for paho

2026-03-27 07:56:57 -07:00

server

fix(go): add nested packet field to WS broadcast, fixes #162

2026-03-27 13:31:37 -07:00