Actions76
- Advert Actions
- Channel Actions
- Contact Actions
- Device Actions
- Export Private Key
- Factory Reset
- Get Allowed Repeat Frequencies
- Get Auto Add Config
- Get Battery Voltage
- Get Custom Variables
- Get Device Info
- Get Device Time
- Get Radio Parameters
- Get Self Info
- Get Self Telemetry
- Get Stats
- Get Tuning Parameters
- Reboot
- Set Advert Name
- Set Auto Add Config
- Set Custom Variable
- Set Device Pin
- Set Device Time
- Set Other Parameters
- Set Path Hash Mode
- Set Radio Parameters
- Set Tuning Parameters
- Sign Data
- Sync Device Time
- Diagnostic Actions
- Flood Scope Actions
- Message Actions
- Repeater Actions
- Utility Actions
Diagnostic → Get Telemetry
AI-generatedSummary
Queries a MeshCore device for its own telemetry data (battery and sensor readings) without requiring radio traffic or a contact key.
Inputs
- extraTimeoutMs — Extra time to wait on top of the device's own airtime estimate. That estimate is computed for the outbound packet, but a trace grows a hash and an SNR byte at every hop, so the reply takes longer than it predicts — raise this on long or slow paths.
Output shape
a single item containing the device's battery voltage and parsed sensor data (Cayenne LPP format).
The node uses a custom implementation (
getSelfTelemetry) because meshcore.js cannot request this telemetry viasendCommandSendTelemetryReq(which requires a public key). The firmware answers with a 4-byte opcode plus reserved bytes, no contact, and no login.
Examples
Example 1: Monitor battery level and temperature of a repeater node.
Use the default timeout (or a longer value if the device is slow), and connect using the MeshCore credential.