Power & Communications

Meshtastic Network in Cumbria

By CumbriaCQ · Updated and source checked

CumbriaCQ no longer operates its former local Meshtastic network or MQTT service. Old CumbriaCQ connection settings should not be used. The local community mesh supported by CumbriaCQ is now MeshCore. This is a change to CumbriaCQ’s service, not a statement that the international Meshtastic project has closed or that nobody else in Cumbria uses it.

What changed locally?

The operator’s forum reply dated 17 November 2025 explicitly says that CumbriaCQ was running MeshCore rather than Meshtastic, and directs users to the UK/EU Narrow preset. The retained CumbriaCQ retirement notice confirms that the old MQTT service and settings are retired. The dated reply establishes that the migration was already in place by then; it is not an exact cutover log.

Older search results, screenshots and saved guides may still describe an active CumbriaCQ MQTT network. Do not use those as current joining instructions. The current local guide has the Maryport dashboard, public MeshCore channels and community discussion links. No old MQTT hostnames, account details or connection QR codes are reproduced here.

What Meshtastic is still useful for

Meshtastic is a separate project for communication using supported LoRa radios. A phone or computer connects locally to a radio through Bluetooth, USB or Wi-Fi where supported. The radios then exchange messages over their own RF path rather than sending ordinary SMS. Suitable standalone devices can offer their own controls.

Two appropriately configured devices can communicate when within usable range; a wider mesh may relay traffic through other participating nodes. Range is not fixed. Terrain, placement, antennas, radio settings, interference and power determine what works. You need compatible endpoints and people to communicate with, not just a phone app.

Radio mesh and MQTT are different layers

MQTT is an optional messaging protocol used to link a radio mesh to an internet-connected server. In the official Meshtastic MQTT guide, a node can use its own network connection or a connected client’s connection to reach a broker. That can connect distant activity, but the internet-dependent portion is not an off-grid radio path.

Consequently, a distant node shown in an app or online map does not prove direct radio reach. Losing a broker can remove internet-linked traffic while a compatible local RF pair still works. Conversely, having working broadband does not fix an obstructed radio path to your own node. CumbriaCQ’s retirement of its MQTT service does not disable unrelated Meshtastic radios or other operators’ services.

Can you reuse a Meshtastic radio for MeshCore?

Possibly, but check the exact model, board revision and frequency variant against the official MeshCore hardware and firmware tools. Shared LoRa hardware does not mean shared protocols. You cannot join MeshCore simply by changing a Meshtastic channel name or installing a different phone app.

  1. Decide whether to move. If your intended contacts still use Meshtastic, keeping a compatible setup may be more useful than changing it. Read the practical comparison.
  2. Preserve what you need. Record your existing configuration securely. Do not post channel keys or account credentials. Changing firmware can erase settings and create a different identity.
  3. Check support and lawful operation. Confirm the precise board is supported in the role you need. UK short-range-device use remains conditional on Ofcom’s equipment and operating requirements; “868 MHz” is not sufficient.
  4. Install the correct firmware. For ordinary phone messaging choose BLE Companion, not Repeater. Use the official board-specific flashing instructions and a suitable data cable. Do not reflash equipment belonging to another operator.
  5. Configure and test afresh. Pair the MeshCore app, select the agreed local radio settings, add the current public channels and arrange a two-way message with a reachable user. Follow our complete MeshCore first-message guide.

If you want to continue with Meshtastic

Use the current official Meshtastic setup guide rather than retired CumbriaCQ instructions. Identify your device, use its supported firmware, configure the appropriate UK region and agree modem settings and channel details with your intended peers. Start with a nearby two-way radio test before adding internet integrations.

Review position sharing and MQTT carefully. The official module documentation explains that disabling MQTT encryption can send packets unencrypted to a broker even when radio-channel keys are configured. Do not assume a public default channel is confidential.

Help and sensible expectations

For CumbriaCQ’s current local direction, visit MeshCore Cumbria or ask in the MeshCore forum. Explain whether your device is still running Meshtastic or has already been reflashed; that avoids troubleshooting the wrong protocol.

Neither mesh is a guaranteed way to summon help. Keep official warnings and normal emergency contact routes first, use 999 or 112 in immediate danger through a working phone, and agree a fallback if a check-in receives no reply. Our radio and internet dependency guide explains how to assess the whole path.

Your next step

Explore Power & Communications · Ask the CumbriaCQ community

Sources and further reading

Source links were checked for this update. Official instructions and manufacturers’ guidance take precedence. How these guides are prepared.