Understanding What You're Seeing in the App

Understanding What You Are Seeing in the App

The Meshtastic app surface area can seem dense at first. This page decodes the most important numbers and indicators you will encounter day-to-day, so you can read the mesh like a map instead of a wall of jargon.

SNR (Signal-to-Noise Ratio)

SNR is displayed in dB (decibels) and measures how much stronger your desired signal is compared to the background noise. In LoRa:

• Positive SNR (e.g., +5 dB): Strong signal, well above the noise floor. Excellent conditions.
• Slightly negative SNR (e.g., -5 to -8 dB): Normal for LoRa. The spread-spectrum modulation allows LoRa to decode packets even when the signal is below the noise floor - this is one of LoRa key advantages over conventional radios.
• Very negative SNR (e.g., -15 dB or worse): The signal is barely decodable. Packets at this level will have high error rates. Increasing distance or obstacles will push it past the decoding threshold entirely.

A rough rule: anything better than -10 dB SNR is good for reliable communication. Below -15 dB, expect occasional dropped packets.

RSSI (Received Signal Strength Indicator)

RSSI measures the absolute power of the received signal in dBm (decibel-milliwatts). Unlike SNR, RSSI does not account for background noise - it is just the raw signal level.

• -90 dBm or better: Excellent for LoRa. Short to medium range with good antenna alignment.
• -100 to -110 dBm: Typical for medium range or one hop through a building.
• -120 dBm: Approximately the noise floor. Packets at this level are at the edge of decodability.
• -130 dBm or worse: Below noise floor - the signal will not decode reliably.

LoRa sensitivity goes down to around -137 dBm under ideal conditions with high spreading factors, which is why it achieves multi-kilometer range with milliwatt transmit power.

Via 2 hops - what does this mean?

When a message shows via 2 hops, it means the packet traveled through 2 intermediate relay nodes to reach you. A direct connection (0 hops) means your node heard the sender radio transmission directly. Hops increase latency slightly and are subject to the hop limit (default 3), meaning a packet can traverse at most 3 intermediate nodes before being dropped.

Battery icon

The battery percentage shown for each node in the node list is reported by that node itself and transmitted as telemetry. It represents the battery voltage converted to a percentage by the remote node firmware. Values of 0% or 100% sometimes indicate the node is on USB power (and the firmware reports full charge) or that telemetry is not configured. 0% does not necessarily mean the node is dead - it may just mean it is plugged in and the firmware reports nominal voltage.

Last heard timestamp

This is when your node most recently received any packet from that node - whether a message, a position report, or a telemetry update. Nodes that broadcast position or telemetry on a schedule will update this timestamp even when no messages are being sent. If last heard is more than an hour ago, the node may be out of range, powered off, or on a slow telemetry interval.

Channel utilization percentage

This is the fraction of airtime on your channel that has been used by transmissions in the recent window (typically the last 15 minutes). It includes your own transmissions and every packet your node hears from others. The Meshtastic project recommends keeping this below 25%. Above that, collision probability rises quickly because LoRa is a half-duplex medium - only one node can transmit on a channel at a time, and there is no collision detection. High utilization means messages are failing silently.

Node ID format - what is !ab12cd34?

Every Meshtastic node has a unique node ID in the format !xxxxxxxx where the eight hex digits represent the last 4 bytes of the device hardware MAC address. For example, !ab12cd34 means the MAC address ends in AB:12:CD:34. This ID is permanent and tied to the hardware - it does not change when you re-flash firmware or change settings. It is used internally for routing addressed messages and for deduplication in the mesh protocol.