MeshCore UK beginner setup: from a new radio to your first message

To send a MeshCore message from a phone, you normally need the MeshCore app and a supported LoRa radio running BLE Companion firmware. The phone uses Bluetooth to reach that radio; LoRa carries the message to another compatible radio, directly or through repeaters. Installing the app alone does not give your phone LoRa capability. Set up and practise while you still have internet access.

1. Decide who will receive your message

For a predictable first test, arrange a session with a friend and use two companion radios, one for each person. If you have only one radio, you need an existing reachable user. A repeater forwards traffic but is not a second human correspondent. This follows the official MeshCore getting-started advice.

Ask a nearby community which radio profile it uses before purchasing. MeshCore is not a single guaranteed UK-wide network. If your intended friends use Meshtastic, the same-looking box will not make the protocols compatible: read MeshCore versus Meshtastic. Cumbria users should also read the local channels and network guide; the rest of this page is general UK guidance.

2. Check the complete kit, not just its name

• A board and exact revision supported by the official MeshCore hardware links and flasher, in a radio-band version suitable for your intended UK configuration.
• The correct antenna and connector, a usable enclosure and a documented power supply or battery. Check whether batteries and charging parts are actually included.
• For phone use, BLE Companion firmware — not USB-only Companion or Repeater firmware. A product supplied with Meshtastic may need reflashing.
• A compatible phone with Bluetooth, the official MeshCore app and a charged battery.
• If flashing is needed, a computer and a USB data cable, not a charge-only cable. Follow the exact board’s bootloader instructions.

Supported families include Heltec, RAK, Seeed and LILYGO devices, but support varies by exact model, firmware role and revision. Do not buy from a family name alone. A standalone messenger can replace the phone interface, but needs its own supported firmware. The official FAQ explains these choices. This is documentation-based guidance, not a hands-on product test.

3. Establish lawful UK settings before transmitting

Licence-exempt operation requires both the equipment and its use to meet the relevant UK short-range-device conditions. Check the manufacturer’s UK conformity information and the applicable frequency, radiated-power and spectrum-access limits in Ofcom’s SRD guidance and linked IR2030. Antenna gain matters to radiated power; changing antennas or adding an amplifier can change compliance.

A seller’s “868 MHz” label, a firmware download or selecting a preset does not establish legality. Duty cycle means the permitted proportion of time transmitting, where that limit applies. Do not defeat limits to send more traffic. If you cannot establish that the hardware and intended settings comply, resolve that with the supplier or Ofcom before transmitting.

4. Install or confirm the correct firmware

1. Read the instructions for your exact device and fit its correct antenna before powering the radio. Charge it using the manufacturer’s specified supply.
2. If it is already supplied with suitable MeshCore BLE Companion firmware, confirm the version and role rather than reflashing unnecessarily.
3. Otherwise open the flasher through meshcore.io. Select the exact board and BLE Companion role. Follow the flasher’s browser and connection instructions; USB/serial support differs between browsers and boards.
4. Connect with the data cable. Put the device into its documented flashing mode if asked. Close other software using the same serial port.
5. Read any erase warning, retain any existing configuration you need securely, then follow the firmware installation instructions. Keep the connection powered until completion.
6. Restart as directed. Check the displayed firmware/role. Do not use a firmware file intended for a similarly named board.

Firmware installation replaces software on the radio and can erase settings. The official FAQ’s hardware-specific troubleshooting is the next step if the device is not detected; repeatedly trying unrelated firmware is not.

5. Pair the phone and set up the radio

1. Install the app using the Android or Apple links on the official site. Complete downloads before travelling out of coverage.
2. Power your companion, bring it close to the phone and enable Bluetooth. Grant the app the nearby-device/Bluetooth permissions your operating system requires.
3. Open the app’s connection screen and select your companion. Use its displayed or documented pairing code if prompted. Do not assume a repeater will appear as a companion.
4. Give the node a short, recognisable name. Review position sharing before enabling it; a name and location can reveal your home or movements.
5. Open the radio settings and choose the profile agreed by the people you intend to contact. CumbriaCQ currently documents UK/EU Narrow. Other local groups may differ. Save the change and reconnect if the device restarts.
6. On both test radios, check matching frequency, bandwidth, spreading factor and coding rate. These describe how the LoRa signal is transmitted. A matching channel name cannot repair mismatched radio settings.

MeshCore explains that presets are suggestions distributed through its app API, not regulatory approval. Record the working values while online. Leave experimental settings alone until you understand the local mesh’s requirements; the FAQ warns that newer path formats are not understood by older repeaters.

6. Exchange a first message

1. Start with both users in a safe nearby location, with some separation between radios and antennas unobstructed. Confirm that both apps show their companion connected.
2. Add the same channel on both devices. For local public chat, use Add Channel → Join a Hashtag Channel and the agreed name. Treat hashtag channels as public; for confidential household conversation, use the app’s private-channel function and share its key only with intended participants.
3. Use the advert control to announce your node. An advert shares identifying information including the public key, and position if supplied. For the nearby test choose the local/zero-hop option if offered; a flooded advert is relayed by repeaters and is useful for wider discovery.
4. Send one short channel message: “First test from Alex — please reply.” Ask the other person to reply with a different message so you verify both directions.
5. For a direct message, find the other person’s advert in the discovered contacts list and add/accept the contact as your app requires. Select that contact, send a brief message and check the delivery status and their reply.
6. Repeat from the places you actually expect to use the radios. Write down where it succeeds and where it fails. Do not infer dependable coverage from a single unusually good result.

The official FAQ distinguishes direct messages, adverts and group channels. Channel traffic is not a guaranteed mailbox: someone who is out of range can miss it. A delivery indication is not proof that a person has read and understood the message; ask for an explicit reply for an important check-in.

7. Check that your intended path works without internet

After setup, agree the test with your correspondent. Turn off mobile data and internet Wi-Fi on your phone while keeping Bluetooth on. If you use aeroplane mode, re-enable Bluetooth. Exchange a fresh message in both directions. A dashboard or downloaded map is not a substitute for this test. This checks your phone’s local access path; it does not certify every remote node’s power supply or rule out an internet bridge elsewhere.

When it does not work

Companion missing from the app

Check charge, BLE Companion firmware, phone permissions and whether another client is already connected. Use the manufacturer’s pairing procedure; check the official FAQ before resetting.

Bluetooth works but no messages arrive

Compare both radios’ settings and channel keys. Check antennas, use a known nearby peer and move to a safe clearer position. Receiving an old advert does not establish a current route.

One direction works

Ask for a reply and compare both locations, antennas and power supplies. Hearing a powerful high-site node does not prove that it can hear your indoor companion.

It worked yesterday

A repeater, battery or radio path may have changed. Retry calmly with a nearby peer, then ask the local group. Avoid repeated long messages that congest the shared channel.

Keep it useful after the first test

Store the cable with the radio, keep both phone and companion charged, retain offline instructions and agree check-in times and a fallback. Do not post keys, passwords or precise private locations when asking for help. Mesh is an extra tool, not a replacement for official alerts or 999/112. Build it into a household plan and use our internet-dependency guide to understand the remaining weak points.