Thanks for the request! This is well-aligned with the project and I have enough context in the codebase to plan it out.

Background

MeshCore telemetry retrieval has two distinct types, which maps exactly to your "2 separate poll buttons" ask:

Remote Telemetry (LPP) — Cayenne Low Power Protocol sensor data (temperature, humidity, battery, GPS, etc.) retrieved via requestRemoteTelemetry(). Available for all node types (Companion, Repeater, Room Server).
Node Status — Operational stats (uptime, noise floor, RSSI, packet counters, queue depth, etc.) retrieved via requestNodeStatus(). Available for Repeater and Room Server nodes only — Companions don't support this request.

Currently both are driven by an adaptive scheduler that rotates through nodes on a per-node interval (default 60 min, min 1 min). There's no way to trigger an immediate poll.

Proposed Implementation Plan

1. Backend — New on-demand poll endpoints

Add two new routes to src/server/routes/meshcoreRoutes.ts:

POST /api/sources/:id/meshcore/nodes/:publicKey/telemetry/poll-remote
POST /api/sources/:id/meshcore/nodes/:publicKey/telemetry/poll-status

Each endpoint will:

Require configuration:write permission (to prevent RF traffic abuse)
Look up the node, validate the source manager is connected
Call requestRemoteTelemetry(publicKey) or requestNodeStatus(publicKey) on the manager
Decode and store the result in the telemetry table (same path the scheduler uses)
Update lastTelemetryRequestAt in meshcore_nodes
Respect the existing 60-second minimum-between-requests throttle per source (return HTTP 429 if too soon)
Return { success: true, fields: [...] } on success so the UI can show what was received

2. Frontend — Poll buttons in the telemetry config panel

Update src/components/MeshCore/MeshCoreNodeTelemetryConfig.tsx:

Add a "Poll Remote Telemetry Now" button (visible for all node types when telemetry is enabled)
Add a "Poll Node Status Now" button (visible only for Repeater/Room Server nodes)
Both buttons show a loading spinner while the request is in flight
On success: show a brief toast/inline confirmation with how many fields were received
On error (including 429 throttle): show an inline error message
Both buttons are disabled when the user lacks configuration:write permission

3. No scheduler changes needed

The scheduler continues to run on its existing cadence. Manual polls simply reset lastTelemetryRequestAt, so the scheduler will naturally back off until the next interval elapses — no duplicate requests.

Questions before proceeding

Where should the buttons live? The natural place is the existing per-node telemetry config panel (the same panel where you enable telemetry and set the interval). Is that the right location, or would you prefer them somewhere else (e.g. the node detail view, a toolbar)?
Should a manual poll work even when scheduled polling is disabled (telemetryEnabled = false)? My inclination is yes — a manual poll is independent of the schedule — but wanted to confirm.

Once confirmed I'll proceed with the implementation.

Generated by Claude Code

Uh oh!

[FEAT] Manual telemetri poll #3674

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions