mirror of
https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git
synced 2026-08-09 10:13:02 +02:00
Purge dead WS handlers from back when we loaded contacts + chans over WS not API
This commit is contained in:
+8
-8
@@ -142,16 +142,16 @@ app/
|
||||
|
||||
## WebSocket Events
|
||||
|
||||
- `health`
|
||||
- `contact`
|
||||
- `message`
|
||||
- `message_acked`
|
||||
- `raw_packet`
|
||||
- `error`
|
||||
- `success`
|
||||
- `health` — radio connection status (broadcast on change, personal on connect)
|
||||
- `contact` — single contact upsert (from advertisements and radio sync)
|
||||
- `message` — new message (channel or DM, from packet processor or send endpoints)
|
||||
- `message_acked` — ACK/echo update for existing message (ack count + paths)
|
||||
- `raw_packet` — every incoming RF packet (for real-time packet feed UI)
|
||||
- `error` — toast notification (reconnect failure, missing private key, etc.)
|
||||
- `success` — toast notification (historical decrypt complete, etc.)
|
||||
|
||||
Initial WS connect sends `health` only. Contacts/channels are loaded by REST.
|
||||
Note: the frontend WS hook also registers handlers for `contacts` and `channels` events, but the backend never emits them.
|
||||
Client sends `"ping"` text; server replies `{"type":"pong"}`.
|
||||
|
||||
## Data Model Notes
|
||||
|
||||
|
||||
Reference in New Issue
Block a user