This Method Is Superseded
The Meshtastic Android app now includes a built-in Local TAK Server that ATAK connects to directly, no plugin, no plugin-to-app version pinning, no separate compatibility matrix. Almost everyone should use that method instead: see the ATAK over Meshtastic guide.
Why this page still exists: The Meshtastic ATAK Plugin still works. If you're on an older Android device that can't run current Meshtastic app versions, have a setup you don't want to touch, or have some other specific reason to stick with the plugin, this page documents that path. For everyone else, it's a dead end, go use the current guide.
Why Version Numbers Matter for the Plugin
Meshtastic uses Protocol Buffers (protobufs) for data serialization, and the protobuf definitions have changed across firmware releases. With the plugin approach, if your firmware, app, and plugin versions didn't align exactly, you'd end up in a non-functioning mesh quagmire where devices couldn't properly communicate. This fragility is one of the main reasons the built-in Local TAK Server replaced this method.
Last known-good interoperability matrix:
- ATAK-CIV: 5.6.0
- Meshtastic ATAK plugin: v1.1.42
- Meshtastic Android app: v2.7.13 (2.7.14 will not work.)
- Meshtastic Firmware: v2.7.15 (2.7.26 will not work.)
If you're setting this up fresh, disable automatic updates on ATAK & Meshtastic in the Play Store so you don't drift off these versions. This matrix may drift further out of date over time since this method is no longer actively tested.
If Meshtastic ↔ ATAK breaks:
Meshtastic Radio Configuration
This part hasn't changed, it's the same radio-side tuning covered in the current guide (ShortTurbo preset, private encrypted channel, TAK/TAK_TRACKER device role, Smart Position, etc.). Configure your Meshtastic device the same way regardless of which bridge method (plugin or Local TAK Server) you use.
ATAK Plugin Configuration
Navigate to: Settings → Tool Preferences → Specific Tool Preferences → Meshtastic Preferences
Mesh Settings
| Setting |
Value |
Explanation |
| Meshtastic Channel Index |
0 |
Use your private primary encrypted channel. Set a different value if using a different channel for ATAK. |
| Filter by Channel Index |
On |
Ignore traffic on other channels if you have multiple channels configured. |
| Hop Limit |
3 |
Good starting point. Controls how many mesh hops a message can make. Adjust based on network size. |
| Request ACK |
Off |
Don't need acknowledgments, just extra mesh traffic. Turn off for scalability. |
PLI & Reporting
| Setting |
Value |
Why |
| Limit PLI Reporting Rate |
On |
Keeps the mesh clean by throttling position updates. |
| PLI Reporting Interval |
1 minute |
Balance between situational awareness and bandwidth conservation. |
| Only Send PLI and Chat |
Off |
We want to send data packages, GRGs, etc., not just position and chat. (You may want to disable this if you are using a LoRa preset other than ShortTurbo) |
| Send Read/Delivery Receipts |
Off |
Extra traffic we don't need. Save bandwidth. |
Display Settings
| Setting |
Value |
Effect |
| Show Meshtastic Devices |
On |
See standalone TAK_TRACKER devices and ATAK EUDs on the map. |
| Hide Devices Without GPS |
Off |
Personal preference. Some prefer to see every device in geochat even without position. |
| Hide Local Node |
On |
Shows your usual Blue Arrow in ATAK without a duplicate Meshtastic icon. Cleaner display. |
Server Relay
| Setting |
Default Value |
Gateway ATAK EUD |
| Relay to Server |
Off |
On (for gateway only) |
| Relay from Server |
Off |
On (for gateway only) |
Critical: Only enable these on one EUD. That EUD becomes your "gateway" between your ATAK server and mesh network. It must have internet access. All other EUDs should have these turned off to avoid a traffic relay nightmare.
File Transfer
| Setting |
Value |
Notes |
| Enable File Transfer |
On |
ShortTurbo has some bandwidth. Use it. (Or, disable this if you use a different LoRa preset & only want chat/position data) |
Audio & Voice
| Text to Speech |
Off |
Enable if you want ATAK to read messages aloud. Personal preference. |
| PTT KeyCode |
Off |
Push-to-talk feature, off unless you're using it. |
GPS Settings
| Use Meshtastic GPS |
On |
Use the Meshtastic device's GPS for position data. |
Encryption
| Enable Extra Encryption |
Off |
Only enable if you need to encrypt already-encrypted packets. Usually unnecessary. |
| Encryption PSK |
Unset |
Leave blank unless double-encrypting. |
Troubleshooting
Common Issues:
- Nodes see each other but ATAK doesn't show them: Check channel index settings. Make sure the ATAK plugin is using the same channel as your encrypted Meshtastic channel.
- Messages not getting through: Check hop limit. Start at 3, adjust if needed. Verify encryption is configured the same on all nodes.
- Poor performance: Confirm you're using ShortTurbo, not LongFast. LongFast lacks bandwidth for ATAK traffic.
- Firmware version conflicts: Verify all devices are on compatible firmware (2.7.x series). Check app version matches firmware series.
- Gateway not bridging to server: Only one Meshtastic-enabled ATAK EUD should have "Relay to/from Server" enabled. Verify that EUD has internet connectivity.
- Plugin shows "disconnected": BLE connection lost or plugin crashed. Reconnect Bluetooth in the Meshtastic app, then restart the ATAK plugin.
