The Meshtastic Android app handles the communication and shows the location of everyone in your private group. Each member of your private mesh can always see the location and distance of all other members and any text messages sent to your group chat.
Open the App and you should see a screen like this. You can move through the tabs but nothing much will be visible until you connect to a radio device.
You will need a device with Meshtastic installed to go any further. See the getting started section for information on how to do this.
Open the Settings tab (last tab), and it should look similar to the screen below. It shows any Meshtastic devices that are found over Bluetooth.
- Select the Device by name, "Meshtastic_c830" in the example below. (You will see any active devices within range, so make sure to get the right one.)
- You will need to "pair" the device by entering a PIN shown on the device screen. This can alternatively be done in the phone Bluetooth settings. If the Device has no screen, but it's connected via USB, it may be displayed on a serial terminal (921600 Baud). For a development device, the PlatformIO terminal would come in handy. Some nodes have buttons allowing you to change the page displayed on the nodes screen. If you double click this button, it will set the pairing code to
- Edit the "Your name", e.g. to be "Mike Bird". This is the name that other people will see, so make it unique within your group.
- The initials e.g. "MB" should also be unique and will be used to identify you in the message history and on the device screens.
- This should start the communication with the Device. The cloud icon, on the status bar, will have a tick.
If there is no Device shown, just the
None (disable) as below, then the device may be off, or in a sleep mode. Try to reset, or press a button to wake it.
The cloud icon at the top right corner indicates if you are connected to a device. This currently has three states:
Cloud with a slash through it: No device connected to the application.
Cloud with a tick in it: Device connected to the application.
Cloud with an up arrow in it: Device is connected, but currently sleeping or out of range.
Once you are connected to a Device the App will work, and you can test it by "sending" a message. However you will need to join or create a new mesh network so you have someone to communicate with. If you have been sent a QR code or link for Meshtastic, then skip ahead to Join a Channel, otherwise you will need to Setup a Channel.
To use Meshtastic you need to setup a Channel, and share the details with your group. The group is private and only those who have the details can join the group and see the messages. You will need to do this once initially, and then only when you want to change or make a new mesh network group. For a new device you will see there is a default setting, shown as
#LongSlow-1, Very long range (but slow). It is OK to use this initially.
The Channel tab allows you to do this. This screen is initially locked, so that you don't change it accidentally. Press the lock symbol, and you will be able to edit. First, select the Channel options, as shown here, and chose the most appropriate option:
Here we selected
Very long range (but slow), and then made a Channel Name using the keyboard. This identifies your group, here "Owl Team".
You will see a warning because changing the Channel will break communications with your group, i.e. if you change your settings without sharing the new details with the group.
The app will generate a new QR code on the screen, and this encodes the channel details and a random 256-bit key for sharing with the new group. You can share the QR code with other Meshtastic users, or use the Share button and share the link via chat message, SMS, email (the link is a very long code, for example: https://www.meshtastic.org/d/#CgUYAyIBAQ
If another user shares a QR code, you should be able to scan it with your camera (phones with Android 9 or later will recognise QR codes).
- You will see a message like Tap here to go to "www.meshtastic.org" in your browser.
- Proceed and it will launch the Meshtastic app, and you should see a message like "Do you want to switch to the 'Owl Team' channel?".
- Accept this, and the app will change to this new channel. You will lose any current channel setting!
If the channel is shared as a link via a message, or email, you can click on the link and follow similar steps.
You must use a link or a QR Code to Join a Channel. Setting the Channel Settings to the same Name and Options will not work as there is also a shared key encoded in the link.
Your app must be connected to an active Meshtastic device for the link or QR Code to work.
You can test changing channels with the QR code shown below.
Various data-rates are selectable when configuring a channel and are inversely proportional to the theoretical range of the devices:
|Short range (but fast)||21.875 kbps|
|Medium range (but fast)||5.469 kbps|
|Long range (but slower)||0.275 kbps|
|Very long range (but slow)||0.183 kbps (default)|
The message window operates like any chat applications. Note that any messages sent go to the whole group, and there is no one-to-one message feature.
With LoRa (or any radio) there is some uncertainty that the messages has been received, so there is a confirmation built-in to the protocol. There are small cloud icons shown to the right of the messages you send:
- Cloud with an up arrow: the application is waiting for the device to some out of sleep mode (or come back into bluetooth range), to upload the message to the device.
- Cloud only: message has been sent via Bluetooth and transmitted via LoRa.
- Cloud with a check mark: message has been delivered to at least one node in the mesh and at least one node sent back a confirmation (successfully received by the initial sender).
- Cloud crossed out: message may have been delivered to at least one node in the mesh. If at least one node sent a confirmation back the initial sender did not receive the confirmation within a certain timeout.
Thus, in a group size of 3 and up, confirmations could be from any one device (not person), so it is good practice to respond, so the initial sender knows you have read their message.
There is no long-term store-and-forward of messages, so messages not received within a time-out (duration?) are lost.
The network list shows all the users (devices) that have connected to the same Channel. For each entry, it shows the last time they were active, their distance, and their last known power status (battery & percentage, or external power). In the example below, Lora V2 is the local user, m8n was last heard from 3 minutes ago and is 29m away, and 25C is active and 498m away.
This is a list of network nodes, rather than users, so where there is a named user connected to the device, you will see the user name, otherwise the node is shown as
Unknown a3c9 (where
a3c9 is the last 4 hex digits from the MAC address.)
The Map tab will show a local map with an icon for each active mesh node that has a known position. The users names are shown against the icon.
The map is not developed by the Meshtastic project, and the source of the mapping system is Mapbox (free-tier), and the map data is sourced from OpenStreetMap OSM. Mapbox currently requires analytics to be enabled for you to use their mapping system. There is currently no off-line maps (phone needs mobile data or wifi), although this will be improved in the future. If you don't see the features that you'd expect on the map then head over to OpenStreetMap OSM where you can contribute new data to the map.
Pressing the three verticle dots in the top right corner shows the configuration menu.
This allows you to change the frequency with which your location is broadcast across the mesh. By default this is set to 900 seconds (15 minutes). The minimum time this can be set to is 375 seconds, the reasons for which have been discussed on the forum.
To use as little power as possible while running on battery, ESP32 based devices go into a sleep mode. Unfortunately, during this sleep mode they turn off their Bluetooth radio. They can be woken early from this sleep by either receiving a message over LoRa (the LoRa receiver never switches off), of by pressing a program button where there is one on the device. This setting allows the length of the sleep mode to be changed from the default of 300 seconds (5 minutes). Setting the period to 0 seconds disables the sleep function on the device.
The debug page allows you to see all packets sent between the application and the device. This can then be used for debugging purposes.
This allows you to save your messages to a .csv (comma sparated value) file on your phone.
This allows you to change between light and dark themes, or to select the system default.