rf_sentinel / guides / sentinel-link-setup
Sentinel Link setup
Sentinel Link lets RF Sentinel phones share what they detect: each phone of a group shows the devices the others hear on its list, radar and map, marked VIA with the phone's name. Phones reach each other three ways, and you can use any mix of them.
| Path | Reach | Needs | Speed |
|---|---|---|---|
| Bluetooth | About 10 to 30 m | Nothing extra | Everything, right away |
| Meshtastic | Kilometres, more through other nodes | One Meshtastic LoRa node per phone | A few devices per packet, one packet a minute by default |
| Internet relay | Anywhere with mobile data | An MQTT broker, ideally your own | Up to 8 packets every 5 s |
Every path needs the phones to be linked into a group first (step 1). All of them only share while a scan runs, and everything is encrypted with the group's key.
1. Link the phones (once)
- Install the same RF Sentinel version on every phone.
- On each phone: Settings → Sentinel Link → Open Sentinel Link, and fill in This phone's name. It's the name the others see next to VIA and in "via NAME" alerts.
- Put the two phones side by side. Tap Link up a Sentinel on one and Join a Sentinel on the other. Allow "Nearby devices" if Android asks.
- Both screens show a 6-digit code. Same code on both: tap Confirm on both. Different code: Cancel on both and start again.
- A third phone joins the same way, from any phone already in the group.
The phones agree on the group's key through that code; a phone that wasn't there can't read the group. To leave, tap Leave the group: that phone forgets the key and stops sharing.
2. Bluetooth (phones nearby)
On by default once linked (Share over Bluetooth). Start a scan on both phones: the status reads "Sentinel Link · 1 Sentinel linked" when they're in range, and they find each other again by themselves after going out of range. Their devices show under the Sentinels chip.
For phones that are always far apart, turn Share over Bluetooth off and use one of the paths below, so the status doesn't sit on "waiting for Sentinels".
3. Meshtastic (phones kilometres apart)
What you need
- One node per phone: a LoRa board running the official Meshtastic firmware, for example a Heltec V3, a LilyGO T-Beam, or a Seeed XIAO ESP32S3 with its Wio-SX1262 LoRa board. A plain ESP32 has no LoRa radio.
- Its antenna, always screwed on before the node is powered.
Prepare each node in the Meshtastic app
- Flash the official firmware if the board doesn't have it (Meshtastic's web flasher).
- Connect to it with the Meshtastic app and set Settings → LoRa → Region to your country's region. A node without a region doesn't transmit.
- Give both nodes the same modem preset (the default, Long Range - Fast, is fine), the same frequency slot and the same primary channel (channel 0). Leaving every node on the defaults does all of that.
- Check they hear each other: each node should list the other in its node list, and a text sent from one reaches the other.
- Disconnect the Meshtastic app from the node: a node serves one app at a time.
Connect the node to RF Sentinel
- Sentinel Link screen → Meshtastic node → turn on Use a Meshtastic node.
- Tap Choose a node and pick yours from the list. If Android asks for a PIN, it's on the node's screen, or
123456. - Start a scan. The status goes through "reading its settings…" and "adding the RFSentinel channel…" to "Meshtastic node · channel N, encrypted".
- Do the same on the other phone with its own node.
RF Sentinel adds a private channel named RFSentinel to an empty slot (1 to 7) of the node, with a key made from the group's key. It never sends on the primary channel 0 or a channel you set up, and never to Meshtastic's MQTT. Strangers' nodes may relay your packets but only see encrypted bytes. Within a minute of both phones scanning, the node line reads "heard X ago".
Settings on the Sentinel Link screen
| Setting | What it does |
|---|---|
| Alert for what they hear | Alerts for devices that arrive this way. Each path has its own switch, so the mesh can stay quiet while nearby phones still alert, or the reverse. |
| Send a packet every | 15 s to 5 min, 60 s by default. Watchlist matches go out sooner anyway. Shorter sends more devices but uses more air time on a mesh others share. |
| Hops | 1 by default: only nodes in range of yours pass it on. Raise it when your nodes reach each other only through other nodes (at most your node's own hop limit). |
| Channel slot on the node | Automatic takes the first empty slot. Pick a slot only if you want the channel in a particular place; a slot holding another channel is never changed. |
| Silence the node's buzzer | Turns off the node's buzzer, vibration and LED alerts; switched back on when you turn this off. The node may restart once. |
What gets through
A LoRa packet holds about 6 to 19 devices. Watchlist matches go first (within about 20 s, then every minute while heard), flagged devices every 3 minutes, everything else once and again every 15 minutes. Only devices heard in the last 2 minutes are sent, and whitelisted devices never. The receiving phone keeps them listed for 16 minutes. For the most complete picture, keep the sending phone's screen on: with the screen off Android allows only a few WiFi scans an hour.
4. Internet relay (phones anywhere)
Every phone of the group connects to the same MQTT broker. Packets are encrypted with the group's key before they leave the phone and go on a topic made from that key, so the broker only sees encrypted bytes, your IP address and when you send. It uses a few small packets a minute of mobile data and carries far more than LoRa: up to 8 packets every 5 seconds.
- Sentinel Link screen → Internet relay → turn on Use an MQTT broker.
- Broker:
mqtts://broker.example.com(encrypted, port 8883 unless you add one) ormqtt://host:port(unencrypted: the username and password travel in clear, so only on a network you trust). - Username and Password if the broker asks for them.
- Check the certificate: leave on. Turn it off only for your own broker with a self-signed certificate.
- Same broker on every phone, then start a scan: the status reads "Connected to HOST". Devices from the relay show under the Mesh chip.
Running your own broker
Any MQTT 3.1.1 broker works. With Mosquitto on a server you control, a minimal setup with a password and a TLS certificate (for example from Let's Encrypt) looks like this:
# /etc/mosquitto/conf.d/rfsentinel.conf
listener 8883
certfile /etc/letsencrypt/live/broker.example.com/fullchain.pem
keyfile /etc/letsencrypt/live/broker.example.com/privkey.pem
allow_anonymous false
password_file /etc/mosquitto/passwd
Create the user with mosquitto_passwd -c /etc/mosquitto/passwd sentinel, open port 8883 in the firewall, restart Mosquitto, and enter mqtts://broker.example.com with that username and password on every phone.
5. A phone that only watches
A phone left in the car or at home can show only what the others send: on its Sentinel Link screen, turn on Show only the other Sentinels. While it's in a group it 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, and hardware plugged into it keeps working. Leave it off on the phones that do the detecting.
6. Check it works
- Members list on the Sentinel Link screen: each Sentinel shows how it's reached, "Linked now", "Over the mesh · last heard X ago" or "Over the internet relay · last heard X ago".
- Main list: rows from other phones carry a VIA badge with their name; the Sentinels chip filters Bluetooth ones, the Mesh chip mesh and relay ones.
- Something stuck? Every status line and its fix is in Sentinel Link troubleshooting.
Q&A
Does Sentinel Link need the internet?
No. RF Sentinel's Bluetooth and Meshtastic links work without any network. Only the internet relay uses mobile data, and only if you turn it on.
How many phones can be in a group?
RF Sentinel links any number: each new phone joins from any phone already in the group, with the 6-digit code. Over Meshtastic, every extra phone adds packets to the same slow channel, so keep the interval at the default or longer with many phones.
Can two phones share one Meshtastic node?
No. A node talks to one RF Sentinel phone at a time over Bluetooth. Each phone that sends or receives over the mesh needs its own node.
Is it safe to use Sentinel Link on a public Meshtastic mesh?
Other nodes can relay RF Sentinel's packets, but they're encrypted twice, by the RFSentinel channel's key and by the group's key, both made from a key only your phones have. They do see that a node is sending, and when. Your packets also use shared air time, so don't set the interval shorter than you need.
Can I use a public MQTT broker?
It works, since RF Sentinel encrypts everything before it leaves the phone, but the broker's owner sees your IP address and when you send, and a public broker can go down or drop clients. Your own broker is better.