rf_sentinel / guides / sentinel-link-troubleshooting
Sentinel Link & Meshtastic troubleshooting
RF Sentinel's Sentinel Link shares what one phone detects with the others in its group, over Bluetooth nearby, Meshtastic LoRa nodes far away, or an MQTT broker over the internet. When devices don't show up on the other phone, the status lines on the Sentinel Link screen say where it stops. This page goes through each one.
Start here
- Same version on every phone. Update all of them to the latest release. Mesh packets from a different packet version are counted as "from another group or version" and dropped. Mesh devices staying listed until the next resend needs 2.40.1 or later on the phone that receives them.
- A scan must run on every phone. Sentinel Link only shares while scanning ("Links while scanning - start a scan to share", "Starts while scanning").
- Open the Sentinel Link screen on both phones (Settings → Sentinel Link → Open Sentinel Link) and read the status under each section: the top line for Bluetooth, the line under Meshtastic node, the line under Internet relay. Compare the two phones: the tables below say what each line means.
- Know where each row on the list comes from (below): not everything on the watching phone comes from the other phone.
- Still stuck? Settings → External hardware → Export all hardware logs on both phones makes one text file each, with the Bluetooth link, Meshtastic node and internet relay logs (no server name or IP address). Attach them to a GitHub issue.
What the list shows, and from where
| On the list | Comes from |
|---|---|
| VIA badge with a phone's name | Another phone of the group heard it. |
| Sentinels chip | Devices from phones linked over Bluetooth. |
| Mesh chip | Devices from phones reached over Meshtastic or the internet relay. |
| External chip, ESP32 / USB badges | This phone's own hardware. A Meshtastic node also reports the other Meshtastic nodes it hears over the air, including strangers' nodes miles away. Those are not from your other phone. |
| Cells, Aircraft | This phone's own cell modem and the online aircraft feeds. Never shared over Sentinel Link. |
To see only what the other phones send, turn on Show only the other Sentinels on the watching phone's Sentinel Link screen. While it's in a group, that phone stops its own Bluetooth, WiFi, cell tower, GPS spoofing and drone checks and the online aircraft and Waze feeds; your Settings stay as they are. Hardware plugged into it keeps working. Leave this switch off on the phone that does the detecting, or it has nothing to share.
The distance shown for a device heard by a Meshtastic node is a Bluetooth estimate and means nothing for LoRa.
Bluetooth link (phones nearby)
| Status | What it means / what to do |
|---|---|
| Not linked yet | This phone isn't in a group. Tap Link up a Sentinel on one phone and Join a Sentinel on the other, close together, and confirm the same 6-digit code on both. |
| Different codes on the two phones | Tap Cancel on both and start again. A different code means the two phones didn't talk to each other directly. |
| Bluetooth sharing off | "Share over Bluetooth" is off. The Meshtastic and internet relay paths still work without it. |
| Sentinel Link · waiting for Sentinels | Sharing, but no linked phone is in Bluetooth range (about 10 to 30 m, less through walls). Normal when the other phone is far away and you use Meshtastic or the relay instead; turn "Share over Bluetooth" off to hide it. |
| Sentinel Link · N Sentinels linked | Working. Their devices show with VIA and under the Sentinels chip. |
| Sentinel Link: allow "Nearby devices" to link Sentinels | Android → Apps → RF Sentinel → Permissions → Nearby devices → Allow. |
| Sentinel Link: Bluetooth is off | Turn the phone's Bluetooth on. It is also how the phone talks to its Meshtastic node, so turning Bluetooth off cuts the mesh too. |
| Sentinel Link: Bluetooth link failed to start | Turn Bluetooth off and on, then stop and start the scan. |
Meshtastic node: connecting
Each phone needs its own Meshtastic node (a LoRa board with the official firmware), paired over Bluetooth. A node serves one app at a time: while RF Sentinel uses it, the Meshtastic app on that phone can't, and the other way round.
| Status under Meshtastic node | What it means / what to do |
|---|---|
| Off / Choose a node | Turn on Use a Meshtastic node and tap Choose a node. |
| Starts while scanning | Start a scan. |
| not paired - tap here to pair | Tap the line. Android asks for a PIN: it's on the node's screen, or 123456. |
| pairing - enter the PIN Android asks for | Finish the PIN prompt in Android's notification or dialog. |
| allow "Nearby devices" / Bluetooth is off | As for the Bluetooth link above. |
| choose the node again | The saved node is gone (unpaired or reset). Tap Choose a node. |
| connecting… / can't connect / no answer - retrying / stopped answering - retrying | Close the Meshtastic app (it may hold the node), keep the node powered and within a few metres, and make sure it isn't connected to another phone. It retries by itself. |
| not a Meshtastic node | The board chosen doesn't run Meshtastic's firmware. Choose the right one. |
| restarted - retrying | The node rebooted (it can happen once after changing its settings). Wait. |
| set its LoRa region in the Meshtastic app first | A new node has no region and won't transmit. Stop the scan, set the region in the Meshtastic app (Settings → LoRa → Region), then start the scan again. |
| its LoRa transmit is off | Turn "Transmit enabled" back on in the Meshtastic app (Settings → LoRa). |
| no free channel - free one in the Meshtastic app | Channel slots 1 to 7 are all in use. RF Sentinel only takes an empty slot or its own RFSentinel channel; delete a channel you don't need. |
| channel N is in use - pick another slot | The slot chosen under Channel slot holds a channel you set up. Pick another slot or "automatic". |
| couldn't add the RFSentinel channel | The node refused the change. Restart the node, then the scan. |
| channel N, encrypted | Connected and ready. Now see whether packets get through. |
Meshtastic: nothing arrives on the other phone
Once connected, the node line adds "sent X ago" when this phone hands a packet to its node, and what the node has received. Read it on both phones:
| The line says | Where it stops |
|---|---|
| · nothing heard yet | This node hasn't received any packet from any other node since it connected. Its radio isn't reaching the mesh: see the radio checks. |
| · nothing from the group yet (the node hears other traffic) | The node's radio works (it hears other nodes) but nothing from your other phone's node arrives. Check the other node's line, then the radio checks on both nodes. |
| · heard X ago | Packets from the group arrive. If devices are still missing, see only some devices arrive. |
| · N from another group or version | Packets on the RFSentinel channel that this phone can't open: the phones aren't in the same group, or they run different versions. Update both; if it keeps counting, leave the group on one phone and join again from the other (Bluetooth, close together). |
| · N too old (check the phones' clocks) | Packets more than 15 minutes off this phone's clock are refused (so they can't be replayed). Set both phones to automatic date and time. |
"Sent" means the phone handed the packet to its node over Bluetooth. Whether the node transmits it, and whether the other node hears it, is up to the radios.
Meshtastic: radio checks
Stop the scan in RF Sentinel on both phones (or turn off "Use a Meshtastic node"), open the Meshtastic app, and compare the two nodes:
- Antenna screwed on firmly. A node without its antenna barely hears anything, and transmitting without one can damage the radio.
- Settings → LoRa: same Region, same Modem preset (for example Long Range - Fast), same Frequency slot, and transmit enabled. Nodes with a different preset or slot are on another frequency or speed and never hear each other.
- Primary channel (channel 0): same name and key on both. With the frequency slot at 0, Meshtastic picks the frequency from the primary channel's name, so a renamed primary channel moves the node to another frequency. RF Sentinel never touches channel 0.
- Do they see each other? Each node should list the other in the node list with a recent "heard" time and a signal reading. Send a text from one to the other on the primary channel. If that fails, RF Sentinel can't get through either: it's the radios, the settings or the distance.
- Not too close, not too far. Two nodes side by side (under a metre) can overload each other's receivers: keep them a few metres apart. Far apart, LoRa range depends on height and terrain; a node indoors or in a pocket reaches much less.
- Hops (Sentinel Link screen): 1 means only nodes in range of yours pass it on. If your nodes only reach each other through other nodes, raise it to the number of hops between them.
When the text gets through, start RF Sentinel again on both phones. Within a minute the line should change to "heard X ago".
Meshtastic: only some devices arrive
LoRa is slow. Each packet is at most 233 bytes and carries the phone's position and as many devices as fit: about 6 to 19, fewer with long names or matches. One packet goes out per interval (60 s by default, 15 s at the fastest on the Send a packet every slider). Devices take turns:
- Watchlist matches first, within about 20 s, then every minute while heard.
- Flagged devices next, every 3 minutes.
- Everything else once, then every 15 minutes, newest first. 40 ordinary devices take a few packets, so a few minutes at the default interval.
- Only devices the sending phone heard in the last 2 minutes go out. Whitelisted (trusted) devices are never sent.
- The receiving phone keeps a device heard over the mesh for 16 minutes, until the sender's next repeat (2.40.1 and later). Older versions dropped it after about a minute, so only the last packet or two showed.
If devices still go missing:
- Keep the sending phone's screen on, RF Sentinel open. With the screen off, Android allows an app only a few WiFi scans an hour, so the sender hears few networks and has little to send. Bluetooth is limited too.
- Lower the interval on the sending phone (15 s sends 4 times more than the default). More packets use more air time, which a busy public mesh shares with everyone.
- Check the sending phone has the devices: its own list should show them, and "Show only the other Sentinels" must be off there.
Internet relay (MQTT)
| Status under Internet relay | What it means / what to do |
|---|---|
| Off | Turn on Use an MQTT broker on every phone of the group. |
| Set the broker | Enter the broker's address, the same on every phone. |
| Not a broker address | Write it as mqtts://host (encrypted, port 8883) or mqtt://host:port. |
| Starts while scanning | Start a scan. |
| Connecting to HOST… | Wait; if it stays there, the phone has no internet or the broker is down. |
| Can't reach HOST - …, retrying | Wrong host or port, the broker is down, or the network blocks the port. With mqtts:// and Check the certificate on, a self-signed certificate is refused: use a real certificate, or turn the check off only on a broker you run yourself. |
| The broker refused the username or password | Fix the username and password on that phone. |
| The broker refused the connection (code N) | The broker turned the client away for another reason (see its log). |
| Connected to HOST | Working. Devices from the relay show with VIA and under the Mesh chip. Packets are encrypted with the group's key: the broker only sees encrypted data. |
Q&A
RF Sentinel says "sent" over Meshtastic but the other phone shows nothing. Why?
"Sent" only means RF Sentinel handed the packet to the phone's own node. Read the node line on the receiving phone: "nothing heard yet" means its node hears no LoRa traffic at all, "nothing from the group yet" means it hears other nodes but not yours. In both cases the two nodes aren't reaching each other: check the antennas, that both use the same region, modem preset, frequency slot and primary channel, and send a text between them in the Meshtastic app (radio checks).
Why do only a few of the other phone's devices come through Meshtastic?
LoRa carries one small RF Sentinel packet per interval (60 s by default), so devices take turns: watchlist matches, then flagged devices, then everything else, once and again every 15 minutes. Only devices heard in the last 2 minutes are sent, and a sending phone with its screen off scans WiFi only a few times an hour. Update both phones to 2.40.1 or later (devices then stay listed until the next resend), keep the sender's screen on, and lower the interval to 15 s (details).
Why does RF Sentinel list Meshtastic nodes I don't own?
Your Meshtastic node reports the other nodes it hears over the air, and RF Sentinel lists them as external hardware (ESP32 badge, External chip), like any other radio around you. They can be miles away. They don't come from your other phone; those show with a VIA badge under the Mesh chip.
How do I see only what the other phone detects?
On the watching phone, open RF Sentinel's Settings → Sentinel Link → Open Sentinel Link and turn on Show only the other Sentinels. It turns off that phone's own scans and online feeds while it's in a group, without changing your Settings. Hardware plugged into it keeps working. Leave the switch off on the phone that does the detecting.
Sentinel Link says "waiting for Sentinels". Is something wrong?
No. In RF Sentinel it means Bluetooth sharing is on but no linked phone is in Bluetooth range. If the other phone is far away and you use Meshtastic or the internet relay, turn "Share over Bluetooth" off; the other paths keep working.
What does "too old (check the phones' clocks)" mean?
RF Sentinel's mesh packets carry the time they were sent. A packet more than 15 minutes off the receiving phone's clock is refused, so an old packet can't be replayed. Set both phones to automatic date and time.