-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
P1Priority: highPriority: highbackendBackend relatedBackend relatedbugSomething isn't workingSomething isn't working
Description
Problem
In api/live.py line 33, the connection type is hardcoded as "serial" with a TODO comment: # TODO: track actual type. The sensor config supports serial, TCP, UDP, and simulator modes but the status endpoint always reports "serial".
Impact
- Live status endpoint returns misleading connection info
- Harder to debug sensor connection issues
- WebSocket clients can't display actual connection mode
Steps to fix
- Store the active connection type in the sensor state
- Update
/api/live/statusto return the actual type - Track changes when switching connection modes
Files
api/live.py(lines 33, 120-160)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1Priority: highPriority: highbackendBackend relatedBackend relatedbugSomething isn't workingSomething isn't working