Differences

This shows you the differences between two versions of the page.

--- links:meshcore:quickstart:home [2026/09/10 21:54] – [Share your Contact Details (via Advert)] va7fi
+++ links:meshcore:quickstart:home [2026/09/10 22:54] (current) – [Connect to your MeshCore Device] va7fi
@@ Line 1: / Line 1: @@
 ====== MeshCore Quick Start Guide ======
 <WRAP group>
-<WRAP half column>
+<WRAP twothirds column>
 <WRAP center round info 100%>
 This page was adapted from Liam Cottle's [[https://files.liamcottle.net/MeshCore/Documentation/MeshCore_Quick_Start_Guide.pdf |MeshCore Quick Start Guide]] (November 2025).  Our version contains updates and regional settings used on the South West Coast of BC.
 </WRAP>
 </WRAP>
+<WRAP third column>
-<WRAP half column>
 <WRAP center round tip 100%>
 Download an up-to-date [[mpdf>|PDF version]] of this page.
 </WRAP>
 </WRAP>
 </WRAP>
@@ Line 21: / Line 18: @@
   * You can send text messages to other mesh nodes that are in radio range without the internet. This means it still works even when WiFi, Cellular and Starlink are down.
   * Solar powered repeater nodes can be placed on high points to increase messaging range.
 <WRAP centeralign>
 <WRAP half column>
-{{:links:meshcore:quickstart:mqsg-0.png?0x150|}} \\ Two MeshCore nodes, often used as personal //companion// devices.
+{{:links:meshcore:quickstart:mqsg-0.png?0x100|}} \\ MeshCore nodes used as //companion// devices.
 </WRAP>
 <WRAP half column>
-{{:links:meshcore:quickstart:mqsg-1.png?0x150|}} \\ A MeshCore node setup as a //repeater//.
+{{:links:meshcore:quickstart:mqsg-1.png?0x100|}} \\ A MeshCore node setup as a //repeater//.
 </WRAP>
 </WRAP>
@@ Line 36: / Line 34: @@
   * Each person that wants to send messages will need their own companion node.
-===== Download the MeshCore App =====
+==== Download the MeshCore App ====
   * Search for "MeshCore" by "Liam Cottle" on [[https://play.google.com/store/apps/details?id=com.liamcottle.meshcore.android|Google Play]] or the [[https://apps.apple.com/us/app/meshcore/id6742354151 |Apple App Store]].
   * Alternatively, download for Windows, MacOS and Web from [[https://meshcore.io]]
   * You should save an offline copy of the software so it’s available without the internet.
-===== Where to buy MeshCore nodes? =====
+==== Where to buy MeshCore nodes? ====
   * Recommended devices are listed at [[https://meshcore.io]]
   * Alternatively, supported devices listed on [[https://meshcore.io/flasher]] can be purchased online from overseas suppliers such as [[https://aliexpress.com |AliExpress]] or [[https://www.seeedstudio.com/Wio-Tracker-L1-Pro-p-6454.html |SeeedStudio]], or  [[https://ca.robotshop.com/products/seeedstudio-wio-tracker-l1-pro-w-oled-3d-printed-casing |Robot Shop]] in Canada.
+===== Flash the Firmware =====
+<WRAP group>
+<WRAP twothirds column>
+<WRAP center round tip 100%>
+On Linux, you may have to add the "dialout" group to your user.  To do that, type the following in the terminal replacing "USER" with your username and reboot your computer:<code bash>
+sudo usermod -a -G dialout USER
+</code>
+</WRAP>
+</WRAP>
+<WRAP third column>
+<WRAP center round important 100%>
+You should also use a Chromium based web browser like [[https://brave.com/download/ |Brave]].
+</WRAP>
+</WRAP>
+</WRAP>
+If you already have Meshcore installed, download your current settings:
+  * Open the MeshCore app ([[https://play.google.com/store/apps/details?id=com.liamcottle.meshcore.android|Android]], [[https://apps.apple.com/us/app/meshcore/id6742354151?platform=iphone |iOS]], [[https://app.meshcore.nz/|Web App]], [[https://github.com/liamcottle/meshcore.js|NodeJS]], [[https://github.com/fdlamotte/meshcore-cli|Python]])
+  * Navigate to the Settings (the gear in the top right corner)
+  * Scroll down to the "Extra Tools" section and select "Export Config"
+  * "Select All" and click on the check mark in the top right corner to save the ".json" file to your phone.
+Flash the Meshcore Firmware:
+  * Connect the companion device to your computer via USB.
+  * Go to https://meshcore.io/flasher (using a <wrap important>Chromium Browser</wrap>).
+  * Select your device
+  * Select Companion Bluetooth
+  * Select Enter DFU Mode
+  * Select Erase Flash
+  * Select Flash
+To re-load the config file:
+  * Open the MeshCore App
+  * Connect to the companion device, but it probably had a different bluetooth name now
+  * The PIN might be listed on your companion's screen
+  * Skip Setup
+  * Navigate to the Settings (the gear in the top right corner)
+  * Scroll down to the "Extra Tools" section and select "Import Config"
+  * Click on "Select File"
+  * Select the "*.json" file
+  * "Select All" and click on the check mark in the top right corner.
+See [[https://scottbaker.ca/meshcore/getting-started|Scott Baker's article]] for more information.
+<pagebreak>
 ===== Connect to your MeshCore Device =====
   * Turn on your node.
@@ Line 71: / Line 115: @@
 If you’re having trouble pairing with Bluetooth, try rebooting your phone.
 </WRAP>
+<pagebreak>
 ===== Set your Public Display Name =====
 You should now rename your MeshCore node.  The name you choose will be seen by other users on the MeshCore network.
@@ Line 95: / Line 139: @@
 The device name in Bluetooth results will not update until you reboot your node.
 </WRAP>
 <pagebreak>
 ===== Configure Radio Settings =====
-MeshCore can be used all over the world. Different countries have different regulations on
+MeshCore can be used all over the world. Different countries have different regulations on which radio frequencies can be used for public, license free communication. To ensure your node is operating legally, please make sure to select radio settings that are compliant in your country.
-which radio frequencies can be used for public, license free communication. To ensure
-your node is operating legally, please make sure to select radio settings that are compliant
+The MeshCore app provides a list of radio presets that have been suggested by the community for use in specific countries/regions.
-in your country.
-The MeshCore app provides a list of radio presets that have been suggested by the
-community for use in specific countries/regions.
 To configure the radio settings for your MeshCore node:
   * Tap the settings icon in the top right corner.
@@ Line 114: / Line 156: @@
 <WRAP centeralign>
 <WRAP third column>
-{{:links:meshcore:quickstart:mqsg-10.png?0x350|}} \\ Tap the settings icon in the top right corner.
+{{:links:meshcore:quickstart:mqsg-10.png?0x320|}} \\ Tap the settings icon in the top right corner.
 </WRAP>
 <WRAP third column>
-{{:links:meshcore:quickstart:mqsg-11.png?0x350|}} \\ Tap the "Choose Preset" button in the radio settings section.
+{{:links:meshcore:quickstart:mqsg-11.png?0x320|}} \\ Tap the "Choose Preset" button in the radio settings section.
 </WRAP>
 <WRAP third column>
-{{:links:meshcore:quickstart:mqsg-12.png?0x350|}} \\ Tap the radio settings that match the name of your country/region.
+{{:links:meshcore:quickstart:mqsg-12.png?0x320|}} \\ Tap the radio settings that match the name of your country/region.
 </WRAP>
 </WRAP>
@@ Line 135: / Line 177: @@
 See [[https://ridgeline.ve7kod.ca/faq |here]] for more details.
 </WRAP>
 <pagebreak>
 ===== Send a public broadcast message =====
-Messages sent to the Public channel can be seen by anyone on the MeshCore network. They are repeated across the mesh by all repeaters that hear them. Other mesh nodes in range of you or a repeater that rebroadcasted the message, should receive it.
+Messages sent to the Public channel can be seen by anyone on the MeshCore network. They are repeated across the mesh by all repeaters that hear them. Other mesh nodes in range of you or a repeater that rebroadcast the message, should receive it.
 The public channel can be used as a large group chat for general conversation amongst all users on the mesh. It could also be used to send emergency alerts.
-It’s not recommended to send confidential information on the public channel as anyone
+It’s not recommended to send confidential information on the public channel as anyone can read these messages.
-can read these messages.
 To send a message:
@@ Line 174: / Line 206: @@
 <WRAP center round info 70%>
-Outgoing messages will show "Heard 1 repeat" if your node heard a nearby
+Outgoing messages will show "Heard 1 repeat" if your node heard a nearby repeater passing on your message. If there are no nearby repeaters, it will show "Sent". It’s not possible to know who received a channel message.
-repeater passing on your message. If there are no nearby repeaters, it will show "Sent".
-It’s not possible to know who received a channel message.
 </WRAP>
 <pagebreak>
 ===== Share your Contact Details (via QR Code) =====
-Before you can send private, encrypted, direct messages to someone, you and the person
+Before you can send private, encrypted, direct messages to someone, you and the person you send the message to must both add each other as contacts. If the other person doesn’t also add you as a contact, your messages to them will fail to deliver.
-you send the message to must both add each other as contacts. If the other person
-doesn’t also add you as a contact, your messages to them will fail to deliver.
 Contacts can be added in multiple ways:
   * Privately in person by scanning QR Codes.
   * Publicly via the mesh by sending and receiving an "Advert".
 To share your contact details privately via QR Code:
   * Tap the 3 dot menu in the top right.
@@ Line 202: / Line 231: @@
 </WRAP>
 <WRAP third column>
-{{:links:meshcore:quickstart:mqsg-18.png?0x400|}} \\ Show the QR Code to theother person.
+{{:links:meshcore:quickstart:mqsg-18.png?0x400|}} \\ Show the QR Code to the other person.
 </WRAP>
 </WRAP>
@@ Line 238: / Line 267: @@
 </WRAP>
 <pagebreak>
 ===== Share your Contact Details (via Advert) =====
@@ Line 274: / Line 298: @@
 <WRAP center round info 70%>
-Adverts are not encrypted. Sending an advert will share your contact details with
+Adverts are not encrypted. Sending an advert will share your contact details with everyone in range.
-everyone in range.
 </WRAP>
 <pagebreak>
 ===== Send Private Messages =====
-Once you’ve added a contact, and that contact has added you back, you can send private
+Once you’ve added a contact, and that contact has added you back, you can send private messages to each other across the mesh. These messages are encrypted and only the intended recipient can read the message contents.
-messages to each other across the mesh. These messages are encrypted and only the
-intended recipient can read the message contents.
 To send a private message:
   * Tap the contact you want to send a message to.
@@ Line 287: / Line 310: @@
   * The app will try several times to deliver your message to the recipient.
   * If it’s successful, it will show "Delivered" with a check mark.
-  * If an automatic acknowledgement from the recipient is not received after some time,
+  * If an automatic acknowledgement from the recipient is not received after some time, the message will turn red and show as "Failed".
-the message will turn red and show as "Failed".
   * When messages are received, they will show up in the conversation viewer.
-Tap the contact you want to
-send a message to.
+<WRAP group>
-Type a message and press
+<WRAP centeralign>
-the send icon.
+<WRAP third column>
-Received messages will show
+{{:links:meshcore:quickstart:mqsg-25.png?0x400|}} \\ Tap the contact you want to send a message to.
-up in the conversation viewer.
+</WRAP>
-*Note: A message may get marked as failed even though it was successfully delivered to
+<WRAP third column>
-the recipient. This happens if we did not receive the acknowledgment reply from the
+{{:links:meshcore:quickstart:mqsg-26.png?0x400|}} \\ Type a message and press the send icon.
-recipient node. In this case, it’s recommended to send the message again. Once you see
+</WRAP>
-the delivered check mark, you know for sure it was received.
+<WRAP third column>
+{{:links:meshcore:quickstart:mqsg-27.png?0x400|}} \\ Received messages will show up in the conversation viewer.
+</WRAP>
+</WRAP>
+</WRAP>
+<WRAP center round info 70%>
+A message may get marked as failed even though it was successfully delivered to the recipient. This happens if we did not receive the acknowledgement reply from the recipient node. In this case, it’s recommended to send the message again. Once you see the delivered check mark, you know for sure it was received.
+</WRAP>
+<pagebreak>
 ===== Retry sending a failed Direct Message =====
-When you send a direct message to someone, it’s possible that it may not go through after
+When you send a direct message to someone, it’s possible that it may not go through after several automatic attempts. This can happen for many different reasons, such as:
-several automatic attempts. This can happen for many different reasons, such as:
   * Being out of range of the intended recipient.
   * There are no repeaters in between you and the intended recipient.
   * The intended recipient’s radio might be turned off.
   * There might be interference on the radio spectrum.
 To try sending the failed message again:
   * Long press the failed message shown in red.
   * Tap the "Retry Sending" button shown in the message actions popup.
   * Your message will try sending again.
-Long press the failed
-message shown in red.
+<WRAP group>
-Tap the "Retry Sending"
+<WRAP centeralign>
-message action.
+<WRAP third column>
-Your message will try sending
+{{:links:meshcore:quickstart:mqsg-28.png?0x400|}} \\ Long press the failed message shown in red.
-again.
+</WRAP>
-*Note: When sending direct messages, you must both add each other as contacts first.
+<WRAP third column>
-The recipient's companion radio must be turned on to receive the message and to provide
+{{:links:meshcore:quickstart:mqsg-29.png?0x400|}} \\ Tap the "Retry Sending" message action.
-a delivery report. You must also be in radio range of each other, or have a working path of
+</WRAP>
-repeaters between each other.
+<WRAP third column>
+{{:links:meshcore:quickstart:mqsg-30.png?0x400|}} \\ Your message will try sending again.
+</WRAP>
+</WRAP>
+</WRAP>
+<WRAP center round important 70%>
+When sending direct messages, **you must both add each other as contacts** first. The recipient's companion radio must be turned on to receive the message and to provide a delivery report. You must also be in radio range of each other, or have a working path of repeaters between each other.
+</WRAP>
+<pagebreak>
 ===== Ping a Repeater =====
@@ Line 329: / Line 369: @@
   * A green popup will show signal strengths if successful.
   * A red popup will show "Timeout" if your companion didn’t hear the repeater.
-Tap the 3 dot menu icon next
-to a repeater contact.
-Tap the "Ping (Zero Hop)"
-menu item.
-A green popup will show
-signal strengths if successful.
-*Note: Ping tests do not hop through multiple repeaters. You must be in range of the
-specific repeater you are ping testing. For a ping test to be successful, the repeater must
-hear your companion signal directly, and your companion must hear the repeater signal
-directly. If you’re not in range of the repeater, the ping test will fail with a timeout error.
-TODO: This guide is still in progress...
+<WRAP group>
+<WRAP centeralign>
+<WRAP third column>
+{{:links:meshcore:quickstart:mqsg-31.png?0x400|}} \\ Tap the 3 dot menu icon next to a repeater contact.
+</WRAP>
+<WRAP third column>
+{{:links:meshcore:quickstart:mqsg-32.png?0x400|}} \\ Tap the "Ping (Zero Hop)" menu item.
+</WRAP>
+<WRAP third column>
+{{:links:meshcore:quickstart:mqsg-33.png?0x400|}} \\ A green popup will show signal strengths if successful.
+</WRAP>
+</WRAP>
+</WRAP>
+<WRAP center round info 70%>
+Ping tests do not hop through multiple repeaters. You must be in range of the specific repeater you are ping testing. For a ping test to be successful, the repeater must hear your companion signal directly, and your companion must hear the repeater signal directly. If you’re not in range of the repeater, the ping test will fail with a timeout error.
+</WRAP>
+<pagebreak>
+===== TODO: This guide is still in progress... =====
   * Create/Join Private Channels
   * Create/Join Public Hashtag Channels
-  * Backup / Export Config
+  * <del>Backup / Export Config</del>
-  * Restore / Import Config
+  * <del>Restore / Import Config</del>
   * Repeater Trace Tools
   * Discover Nearby Nodes