Captures TELEMETRY_APP (portnum 67) packets in the existing packet handler; record = { from, at /* epoch ms */, kind, data } where kind is the Telemetry oneof case name and data that variant's payload
All eight variants pass through: deviceMetrics / environmentMetrics / airQualityMetrics / powerMetrics / localStats / healthMetrics / hostMetrics / trafficManagementStats (verified against installed @meshtastic/protobufs 2.8.0); bare time-only packets are ignored
uint64 fields serialize as decimal strings via the existing jsonSafe choke point (no BigInt 500s — same class of bug fixed in v0.7.1)
Bounded at 100 like message history, in-memory only, reset on reconnect — noted in Swagger
Bonus fix at the same choke point: protobuf-es internal $typeName keys no longer leak into decoded proto output (also cleaned up /api/device metadata/config sections)
Verification
npm run build ✓
npm test — 37/37 passed (was 34, +3: device+environment variants → from/kind/data; cap at 100 dropping oldest; reset on reconnect)
v0.8.0, CHANGELOG entry added
## What
New `GET /api/telemetry` (+ MCP tool `get_telemetry`) — the mesh's telemetry stream, newest first, last 100 records:
```json
{ "from": 67731772, "at": 1790281651000, "kind": "environmentMetrics",
"data": { "temperature": 4.099999904632568, "relativeHumidity": 81.5 } }
```
## Details
- Captures TELEMETRY_APP (portnum 67) packets in the existing packet handler; record = `{ from, at /* epoch ms */, kind, data }` where `kind` is the Telemetry oneof case name and `data` that variant's payload
- All eight variants pass through: deviceMetrics / environmentMetrics / airQualityMetrics / powerMetrics / localStats / healthMetrics / hostMetrics / trafficManagementStats (verified against installed @meshtastic/protobufs 2.8.0); bare time-only packets are ignored
- uint64 fields serialize as decimal strings via the existing `jsonSafe` choke point (no BigInt 500s — same class of bug fixed in v0.7.1)
- Bounded at 100 like message history, in-memory only, reset on reconnect — noted in Swagger
- Bonus fix at the same choke point: protobuf-es internal `$typeName` keys no longer leak into decoded proto output (also cleaned up /api/device metadata/config sections)
## Verification
- `npm run build` ✓
- `npm test` — 37/37 passed (was 34, +3: device+environment variants → from/kind/data; cap at 100 dropping oldest; reset on reconnect)
- v0.8.0, CHANGELOG entry added
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
New
GET /api/telemetry(+ MCP toolget_telemetry) — the mesh's telemetry stream, newest first, last 100 records:Details
{ from, at /* epoch ms */, kind, data }wherekindis the Telemetry oneof case name anddatathat variant's payloadjsonSafechoke point (no BigInt 500s — same class of bug fixed in v0.7.1)$typeNamekeys no longer leak into decoded proto output (also cleaned up /api/device metadata/config sections)Verification
npm run build✓npm test— 37/37 passed (was 34, +3: device+environment variants → from/kind/data; cap at 100 dropping oldest; reset on reconnect)