ScotMesh Wiki - User contributions [en-gb]

MeshCore/Regions

2026-11-03T17:58:52Z

Admin: Add hig (Highlands) region

{{DISPLAYTITLE:Regions}}
<span id="meshcore-regions"></span>
== MeshCore Regions ==

-----

<div class="sm-cx sm-cx-info">

'''NOTE - A Regional Framework was impelemented in the ScotMesh Meshcore Mesh at the beginning of April 2026. This was out of sheer necessity as our mesh was dying under the flood traffic from England (24,000 flood packets & 600+ messages daily). This saved our mesh from descending into a chaotic, unusable mess of incoherent rambles and frustrated messaging failures. This is why an understaning of regions is imperative to understanding where we are today.'''
</div>

-----

This guide is for '''repeater owners'''.

The aim is simple: keep the scheme readable, predictable, and usable as the network grows.

<span id="why-regions-are-needed"></span>
=== Why regions are needed ===

MeshCore messages travel through repeaters for onward routing. Whilst this is the core function, if every repeater carries every message everywhere, the network becomes noisy, inefficient and flooded with uneccessary traffic.

Regions help us:

# '''Keep local traffic local''' — In the future, a message that only matters in one area wont always need to be repeated across every part of Scotland.
# '''Reduce unnecessary radio traffic''' — LoRa is subject to a finite airtime cycle per hour (compared with Wi-Fi or mobile data), so every avoidable repeat uses valuable airtime.
# '''Improve reliability''' — Less unnecessary repeating leaves more room for useful messages.
# '''Make planning clearer''' — Regions make repeater deployment easier to map, identify needs, plan future expansion and ease of ongoing mesh maintenance.
# '''Support controlled peering''' — Strategic repeaters can deliberately carry neighbouring traffic, such as the '''IOI peering agreement''' between Scotland and the Island of Ireland.

<span id="regions-and-scopes"></span>
=== Regions and scopes ===

There are two related concepts: '''regions''' and '''scopes'''.

{| class="wikitable"
|-
! Term
! Meaning
! Example
|-
| '''Region'''
| A label configured on a repeater to describe the area it serves.
| An Edinburgh-area repeater includes <code>edi</code>.
|-
| '''Scope'''
| A label applied to messages or channels to describe which area (or region) the traffic is intended to travel.
| The <code>#glasgow</code> channel might use <code>gla</code> when traffic should stay in that area.
|}

In a densely populated mesh, a repeater should only carry scoped traffic for regions it genuinely serves. In new or embryonic meshes, this requirment will be a future need but best practise planning mandates introducing regions as early as is practical.

<span id="wildcard-forwarding-is-not-allowed-see-info-box-at-top-of-this-document-for-context."></span>
=== Wildcard forwarding is not allowed (see info box at top of this document for context). ===

The wildcard marker is:

<syntaxhighlight lang="text">*</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

The important rule is: <code>*</code> will appear as a root parent in the region tree, but wildcard forwarding must be denied.

In other words, <code>region put sco *</code> is correct, but must be preceeded by <code>region denyf *</code> .
</div>
The Scottish MeshCore setup does not allow wildcard forwarding. Repeater owners must deny wildcard forwarding with:

<syntaxhighlight lang="text">region denyf *</syntaxhighlight>
You may still see <code>*</code> as the root parent when defining the region tree, for example <code>region put sco *</code>. That is different from allowing wildcard forwarding.

For channel names and suggested scopes, see [[MeshCore/Channels|Channels]].

<span id="scottish-region-code-approach"></span>
=== Scottish region code approach ===

For Scotland, we use simple three-letter lowercase codes.

We are not part of any UK wide mesh (for context see comment box at the top of this documnet) Therefore, '''we are not using any long prefixed names'''

We use short codes such as:

<syntaxhighlight lang="text">sco
cen
fal</syntaxhighlight>
Other countries and communities may use ISO-style hierarchical codes. That is valid for them, but the Scottish convention is designed to be short and easy to read in apps, analyser tools, and community discussions.

<span id="current-june-2026-agreed-region-codes"></span>
=== Agreed region codes ===

{| class="wikitable"
|-
! Code
! Area
|-
| <code>sco</code>
| Scotland — the default scope, carried by every Scottish repeater
|-
| <code>sco-admin</code>
| Scotland-only, for bots and utilities. Never peered out.
|-
| <code>cen</code>
| Central Scotland
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>gla</code>
| Glasgow area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>sti</code>
| Stirling area (proposed)
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>dun</code>
| Dundee area
|-
| <code>per</code>
| Perth area
|-
| <code>hig</code>
| Highlands (Inverness area)
|-
| <code>ioi</code>
| Island of Ireland — peering root beside <code>sco</code>
|-
| <code>wls</code>
| Wales — peering root beside <code>sco</code>
|-
| <code>eng-ne</code>
| North East England — peering root beside <code>sco</code>
|}

<span id="ioi-peering-agreement"></span>
=== IOI peering agreement ===

The Scottish and Irish MeshCore communities maintain a '''peering agreement''': scoped traffic is carried on the other network only where '''both''' sides configure for it.

Under that agreement, Scottish repeaters add the <code>ioi</code> region alongside <code>sco</code> where the Scottish baseline applies, and Island of Ireland repeaters add <code>sco</code> alongside their own region codes in the same spirit. Messages with matching '''scopes''' can then move between the two networks predictably, without relying on wildcard forwarding. For example channel names and typical scopes, see [[MeshCore/Channels|Channels]].

The <code>ioi</code> code is '''not''' a Scottish local region. It marks repeaters and traffic that deliberately participate in that peering.

Do not use:

<syntaxhighlight lang="text">ioi-sco</syntaxhighlight>
Use:

<syntaxhighlight lang="text">ioi</syntaxhighlight>
<span id="peering-with-scotland-other-regions"></span>
==== Peering with Scotland (other regions) ====

If another region wants to peer with Scotland in a similar way, they should already have the following in place:

# '''Wildcard flooding disallowed''' on their repeaters (the same principle as the Scottish setup: deny wildcard forwarding with <code>region denyf *</code>; see [[#wildcard-forwarding-is-not-allowed|Wildcard forwarding is not allowed]]).
# '''Appropriate regions on their repeaters''' so traffic is not forwarded wider than intended, and Scottish repeaters are not flooded with scoped traffic they did not agree to carry.
# '''Neighbouring Scotland in RF terms''' so equipment can '''directly''' peer, rather than assuming long unofficial relay chains.

When that fits your situation, contact the Scottish Mesh community on [https://discord.gg/ytxfyuDmSt Discord] so we can discuss scope names, boundaries, and a safe rollout.

<span id="recommended-hierarchy"></span>
=== Recommended hierarchy ===

Although the hierarchy is not written into the code itself, it can be thought of like this:

<syntaxhighlight lang="text">sco
cen
edi
gla
fal
sti (proposed)
fif
tay
dun
per
hig
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
In plain English:

* <code>sco</code> is for Scotland-wide traffic, and <code>sco-admin</code> is a Scotland-only root for bots and utilities.
* <code>cen</code>, <code>tay</code>, <code>fif</code> and <code>hig</code> are Scottish sub regions.
* <code>edi</code>, <code>gla</code>, <code>fal</code>, <code>sti</code>, <code>dun</code> and <code>per</code> are local areas.
* <code>ioi</code> (Island of Ireland), <code>wls</code> (Wales) and <code>eng-ne</code> (North East England) are peering roots beside <code>sco</code>.

<span id="suggested-repeater-configuration-policy"></span>
=== Suggested repeater configuration policy ===

A Scottish repeater should normally be configured with:

# The country code <code>sco</code>, and <code>sco-admin</code> for Scotland-only utility traffic.
# The peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code>.
# The relevant regional code.
# The relevant local code, if appropriate.
# Any neighbouring codes that the repeater genuinely serves.

<div class="sm-cx sm-cx-warning">

Do not allow wildcard forwarding.

In command line interface (CLI) examples, this means using <code>region denyf *</code>
</div>
<span id="falkirk-central-scotland-repeater"></span>
==== Falkirk / Central Scotland repeater ====

A repeater covering the Falkirk area would usually have:

<syntaxhighlight lang="text">sco
cen
fal
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
<span id="edinburgh-facing-central-scotland-repeater"></span>
==== Edinburgh-facing Central Scotland repeater ====

A repeater that mainly serves Central Scotland but has strong coverage towards Edinburgh might use:

<syntaxhighlight lang="text">sco
cen
edi
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
<span id="fife-repeater"></span>
==== Fife repeater ====

A Fife repeater would usually have:

<syntaxhighlight lang="text">sco
fif
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
If it genuinely provides useful Central Scotland coverage, it may also include:

<syntaxhighlight lang="text">cen</syntaxhighlight>
<span id="scottish-repeaters-and-ioi"></span>
==== Scottish repeaters and <code>ioi</code> ====

Scottish repeaters carry the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> alongside <code>sco</code> and <code>sco-admin</code> — these are included in every repeater script:

<syntaxhighlight lang="text">sco
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
That keeps peering-capable forwarding available where the Scottish baseline is configured. It does not make <code>ioi</code> a Scottish local region.

<span id="good-practice-for-repeater-owners"></span>
=== Good practice for repeater owners ===

Use lowercase region codes. Do not use mixed case such as <code>SCO</code>, <code>Cen</code>, or <code>FAL</code>.

Use agreed codes. For example, use <code>edi</code> for the Edinburgh area, not <code>edn</code>, <code>edinburgh</code>, or <code>gb-edi</code>.

Add only the areas your repeater genuinely serves. A high-site repeater may reasonably serve several areas, but a repeater should not claim every region just because it can occasionally hear distant nodes.

Coordinate before adding new codes. If a new area needs a code, discuss it publicly before using it so that the community does not end up with competing names for the same place.

<span id="suggested-command-examples"></span>
=== Suggested command examples ===

The exact method may vary depending on firmware version and whether you are using the app, web configurator, USB serial, or remote administration. The upstream reference is the MeshCore [https://docs.meshcore.io/cli_commands/ CLI Commands] documentation, especially the region management commands.

<div class="sm-cx sm-cx-info">

New to repeater setup?

Start with [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]], then come back here for the fuller detail.
</div>
On current firmware (1.16+) the whole region tree goes in one <code>region def</code> line, followed by <code>region denyf *</code> and the standard <code>set</code> commands. The easiest way to get the exact script for your area is the [https://meshcore.scotmesh.net/repeater/ ScotMesh repeater builder]; the examples below show what it produces.

For a Central Scotland / Falkirk repeater:

<syntaxhighlight lang="text">region def sco cen fal|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
Then check the result with:

<syntaxhighlight lang="text">region</syntaxhighlight>
For a Tayside / Dundee repeater:

<syntaxhighlight lang="text">region def sco tay dun|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
For a Glasgow-area repeater:

<syntaxhighlight lang="text">region def sco cen gla|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
For a repeater that serves Scotland, Central Scotland, Glasgow, Edinburgh, and IOI peering (<code>ioi</code>):

<syntaxhighlight lang="text">region def sco cen|* gla|cen edi|cen sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

'''Set <code>region default sco</code> on your repeater.'''

Without a default scope, adverts sent by your repeater go out unscoped. Because the Scottish network uses <code>region denyf *</code>, other repeaters will reject those unscoped adverts and will never learn your repeater exists. Setting the default scope to <code>sco</code> ensures your adverts are carried normally across the mesh.
</div>
This is separate from flood forwarding permissions. For more detail, see [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

Always check for an <code>OK</code> response where applicable, and remember to save the configuration so it survives a reboot.

<span id="firmware-and-app-version-notes"></span>
=== Firmware and app version notes ===

Region and scope support depends on MeshCore firmware and app support.

Use the latest stable MeshCore firmware and app available for your device. Older firmware may still pass some traffic, but region management and scope handling may not behave as expected.

MeshCore region filtering was introduced across firmware and app releases, and default scope support was added later. The MeshCore posts [https://blog.meshcore.io/2026/01/20/region-filtering Region Filtering] and [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region] are useful background when checking version behaviour.

<span id="naming-and-publishing-new-region-codes"></span>
=== Naming and publishing new region codes ===

When a new Scottish area needs a code, use these rules:

# Use three lowercase letters.
# Make the code obvious to local users.
# Avoid clashing with existing agreed codes.
# Avoid overly small areas unless there is a real need.
# Discuss the code with the local MeshCore community before publishing it.

Examples of possible future codes might include:

<syntaxhighlight lang="text">sti = Stirling
liv = Livingston
abe = Aberdeen
inv = Inverness
ayr = Ayrshire
bor = Borders</syntaxhighlight>
These are examples only and should not be treated as agreed until the community confirms them.

<span id="common-questions"></span>
=== Common questions ===

<span id="do-regions-replace-normal-meshcore-messaging"></span>
==== Do regions replace normal MeshCore messaging? ====

No. Regions help control where scoped traffic is repeated.

<span id="should-every-scottish-repeater-have-sco-and-ioi"></span>
==== Should every Scottish repeater have the same baseline? ====

Yes. Every Scottish repeater carries <code>sco</code>, plus <code>sco-admin</code> and the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> — these are included in every repeater script.

<span id="should-every-repeater-have-every-scottish-region"></span>
==== Should every repeater have every Scottish region? ====

No. That would defeat the purpose of regions. Repeaters should only list the areas they genuinely serve.

<span id="should-we-use-gb-sco-instead-of-sco"></span>
==== Should we use <code>gb-sco</code> instead of <code>sco</code>? ====

Not for this Scottish scheme. Some wider UK or international guides use ISO-style codes, but the local Scottish agreement is to use short three-letter codes.

<span id="can-a-repeater-be-in-more-than-one-region"></span>
==== Can a repeater be in more than one region? ====

Yes. That is useful for high sites, border areas, or repeaters that genuinely link neighbouring areas.

<span id="can-we-allow-for-compatibility"></span>
==== Can we allow <code>*</code> for compatibility? ====

No. The Scottish MeshCore setup does not allow wildcard forwarding. Use the correct region scope instead.

<span id="summary"></span>
=== Summary ===

Regions give the Scottish MeshCore community a simple way to organise the network as it grows.

Our agreed approach is:

* Use three-letter lowercase codes.
* Use <code>sco</code> for Scotland.
* Carry <code>sco-admin</code> and the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> alongside <code>sco</code> on every repeater.
* Use <code>cen</code>, <code>tay</code>, <code>gla</code>, and <code>fif</code> for major regions where they match coverage.
* Use <code>fal</code>, <code>edi</code>, <code>gla</code>, <code>dun</code>, and <code>per</code> for local areas.
* Use <code>ioi</code> for Island of Ireland traffic under the IOI peering agreement.
* Deny wildcard forwarding with <code>region denyf *</code>.
* Do not use long prefixes such as <code>gb-sco</code> or <code>sco-fal</code> in this local scheme.

This gives us a clean, readable, and expandable foundation for building a coordinated Scottish MeshCore network.

MeshCore/Scopes

2026-11-03T17:58:47Z

Admin: Add hig scope code

{{DISPLAYTITLE:Scopes}}
<span id="meshcore-scopes"></span>
== MeshCore Scopes ==

<div class="sm-cx sm-cx-success">

'''Quick start for most users:''' open the app, go to '''Experimental Settings''', set '''Default Scope Region''' to <code>sco</code>. That is all you need for normal Scottish traffic.
</div>
<div class="sm-cx sm-cx-warning">

'''Watch out:''' if you do not have a suitable '''scope''' set, repeaters on the Scottish MeshCore network wont forward your traffic. You can end up '''shouting into the void'''. Check your default scope and each channel’s scope before you count on messages reaching anyone.
</div>
Scope is the single setting that makes or breaks whether your messages go anywhere on ScotMesh. The channel name is for people — the scope is for the mesh. Set your '''default''' to <code>sco</code>, then adjust per channel when you need something narrower.

<div class="sm-cx sm-cx-info">

'''ScotMesh setup:''' Under '''Experimental Settings''', set the default scope region to <code>sco</code>, and keep <code>ioi</code> available in your scope list as well so you can pick it when you need it. For each channel, set scope to match '''where the traffic should travel'''—for example <code>#edinburgh</code> with <code>edi</code>. On '''<code>#ireland</code>''', you may use '''<code>ioi</code> or <code>sco</code>''': use <code>ioi</code> when the message should ride the Island of Ireland scoped path (IOI peering); use <code>sco</code> when you want the same channel but Scotland-wide scoped carriage on the mesh.
</div>
<span id="why-scope-matters"></span>
=== 🤷 Why scope matters ===

Without scope, repeaters have no way to know whether to carry your traffic. With it, messages travel through exactly the right part of the network.

* Keep Scottish traffic inside Scotland where appropriate.
* Allow controlled traffic to and from the Island of Ireland (IOI peering).
* Reduce unnecessary flooding.
* Keep the network easier to grow.

For example channel names and typical scopes, see [[MeshCore/Channels|Channels]]. For repeater region codes, see [[MeshCore/Regions|Regions]].

<span id="what-region-scope-means"></span>
=== 🗺️ What region scope means ===

Think of scope like a postcode on a letter — it tells the mesh where the message is meant to go.

<syntaxhighlight lang="text">sco = Scotland-wide
edi = Edinburgh area (example local)
ioi = Island of Ireland (IOI peering)</syntaxhighlight>
A message scoped to <code>sco</code> is forwarded by repeaters that carry <code>sco</code>as a region. A message scoped to <code>ioi</code> is forwarded by repeaters that carry <code>ioi</code>as a region. If scope is missing or wrong for your path, the message will go nowhere, it is dropped and ceases to exist.

<span id="wildcard-forwarding-is-not-allowed"></span>
=== 🚫 Wildcard forwarding is not allowed ===

The wildcard marker is <code>*</code>. Do not rely on it for routing — the Scottish MeshCore setup expects explicit region scopes.

In the '''Companion App''', your channel scope should always be a '''real region code''' (<code>sco</code>, <code>gla</code>, <code>ioi</code>, and so on). On '''repeaters''', CLI examples sometimes show <code>*</code> as the '''parent''' in a region tree (for example <code>region put sco *</code>); that is a different idea from wildcard '''forwarding''' and is covered in [[MeshCore/Regions|Regions]].

<span id="documented-scope-codes"></span>
=== 📋 Documented scope codes ===

{| class="wikitable"
|-
! Scope
! Typical use
|-
| <code>sco</code>
| Scotland-wide traffic
|-
| <code>sco-admin</code>
| Scotland-only, for bots and utilities (never peered out)
|-
| <code>cen</code>
| Central Scotland
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>hig</code>
| Highlands
|-
| <code>gla</code>
| Glasgow area
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>sti</code>
| Stirling area
|-
| <code>per</code>
| Perth area
|-
| <code>dun</code>
| Dundee area
|-
| <code>ioi</code>
| Island of Ireland / IOI peering
|-
| <code>wls</code>
| Wales — peering
|-
| <code>eng-ne</code>
| North East England — peering
|}

For most day-to-day traffic in Scotland, '''<code>sco</code>''' is the right default. Use a '''local''' code when traffic should stay in that area, regardless of channel name.

<span id="default-scope-and-per-channel-scope"></span>
=== ⚙️ Default scope and per-channel scope ===

On ScotMesh, set your '''default''' scope region to <code>sco</code>. In the mobile app this is usually under '''Experimental Settings'''. Flood packets from the companion then use <code>sco</code> unless a '''group channel''' has its own scope.

'''Per-channel scope overrides the default.''' Examples:

* <code>#glasgow</code> with <code>gla</code> keeps traffic in the Glasgow-area part of the mesh.
* '''<code>#ireland</code> with <code>ioi</code>''' — message is scoped for the Island of Ireland path (IOI peering repeaters).
* '''<code>#ireland</code> with <code>sco</code>''' — same channel name, but the packet is Scotland-wide scoped; repeaters treat it like other <code>sco</code> traffic.

Keep both <code>sco</code> and <code>ioi</code> in your available scopes so you can switch. For background, see MeshCore [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

<span id="how-to-set-region-scope-in-the-companion-app"></span>
=== 📱 How to set region scope in the Companion App ===

Menus vary by app version and platform; the usual flow is:

<syntaxhighlight lang="text">1. Open the MeshCore Companion App
2. Open the channel you want to use
3. Open the channel options or channel menu
4. Find the region scope option
5. Select or add the region code you need
6. Send with that scope active</syntaxhighlight>
Often the channel menu includes something like '''Set Region Scope''', then you pick or type the code (for example <code>sco</code>, <code>edi</code>, or <code>ioi</code>).

<span id="examples"></span>
=== 💬 Examples ===

'''Scotland-wide'''

<syntaxhighlight lang="text">Channel: #scotland
Scope: sco</syntaxhighlight>
'''Local (example)'''

<syntaxhighlight lang="text">Channel: #glasgow
Scope: gla</syntaxhighlight>
'''<code>#ireland</code> with Island of Ireland scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope: ioi</syntaxhighlight>
'''<code>#ireland</code> with Scotland-wide scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope: sco</syntaxhighlight>
The channel name does not set scope by itself — you still choose <code>ioi</code> or <code>sco</code> (or another code) in the channel settings.

<span id="quick-choices"></span>
=== ⚡ Quick choices ===

* Normal Scottish chat: default <code>sco</code>, or <code>#scotland</code> with <code>sco</code>.
* Local-only: local scope such as <code>edi</code> or <code>gla</code> when traffic should stay in that area.
* '''<code>#ireland</code>:''' <code>ioi</code> for IOI-scoped path, '''<code>sco</code>''' when you want Scotland-wide scoped carriage on that channel.
* Tests: <code>#test</code> with whichever scope you are testing (<code>tay</code>, <code>sco</code>, …).

If you are unsure, '''<code>sco</code>''' is the safe general default for Scottish-side traffic.

<span id="what-to-avoid"></span>
=== ❌ What to avoid ===

* Sending traffic with no region scope.
* Relying on wildcard forwarding.
* Assuming the channel name alone chooses routing.

<span id="summary"></span>
=== 📝 Summary ===

<syntaxhighlight lang="text">Default: sco on ScotMesh
Override per channel when needed
#ireland: ioi OR sco
Local: use the local code when traffic should stay local
Check your companion app is scoped before you send your initial messages</syntaxhighlight>
Getting scope right keeps mesh traffic logical and the mesh relaible, easier to use and simpler to grow.

MeshCore/Channels

2026-11-03T17:58:44Z

Admin: Add #highlands (hig)

{{DISPLAYTITLE:Channels}}
<span id="meshcore-channels-now-and-in-the-future"></span>
== MeshCore Channels (now and in the future) ==

Channels are where the conversation happens. Think of them like group chats — anyone with the right device and scope set can join in. There is nothing stopping you creating your own, but the ones below are the agreed community channels so everyone knows where to find each other.

In the Scottish MeshCore network, what really matters for routing is '''region scope''' — not the channel name. The channel name is for people; the scope is for the mesh.

<span id="channel-name-and-scope"></span>
=== 🏷️ Channel name and scope ===

A channel name and a region scope are related, but they are not the same thing.

For example:

<syntaxhighlight lang="text">Channel: #edinburgh
Scope: edi</syntaxhighlight>
The channel name is what you see. The scope is what tells the mesh to carry your message through Edinburgh-area repeaters.

<div class="sm-cx sm-cx-info">

Joining a channel does not automatically set the scope.

Before sending, check the channel settings in the Companion App and make sure the scope matches where you want the message to travel.
</div>
<span id="current-2026-and-proposed-2027-and-beyond-channels"></span>
=== 📡 Current (2026) and proposed (2027 and beyond) channels ===

The following table lists known community channels and proposed channels for Scotland.

'''Type is documentation only; it is not a Companion App setting'''. It groups channels by how you pick them: '''Wide''' for large-footprint traffic (whether the scope is <code>sco</code> or <code>ioi</code>), '''Regional''' for Scottish region area channels, and '''Local''' for Scottish City / town / metropolitan areas. Set '''Scope''' to match the reach you want.

{| class="wikitable"
|-
! Channel
! Type
! Scope
! Status
! Use
|-
| <code>#scotland</code>
| Wide
| <code>sco</code>
| Current
| General Scotland-wide MeshCore traffic.
|-
| <code>#ireland</code>
| Wide
| <code>ioi</code> or <code>sco</code>
| Current
| General Island of Ireland traffic.
|-
| <code>#norniron</code>
| Wide
| <code>ioi</code> or <code>sco</code>
| Current
| Northern Ireland Traffic
|-
| <code>#thenorf</code>
| Wide
| <code>eng-ne</code>
| Current
| North East England traffic.
|-
| <code>#northeast</code>
| Wide
| <code>eng-ne</code>
| Current
| North East England traffic.
|-
| <code>#highlands</code>
| Regional
| <code>hig</code>
| Current
| Highlands traffic (currently used around Inverness).
|-
| <code>#central</code>
| Regional
| <code>cen</code>
| Proposed
| Central Scotland traffic.
|-
| <code>#dundee</code>
| Local
| <code>dun</code>
| Proposed
| Dundee area traffic.
|-
| <code>#edinburgh</code>
| Local
| <code>edi</code>
| Proposed
| Edinburgh area traffic.
|-
| <code>#falkirk</code>
| Local
| <code>fal</code>
| Proposed
| Falkirk area traffic.
|-
| <code>#fife</code>
| Regional
| <code>fif</code>
| Current
| Fife area traffic.
|-
| <code>#glasgow</code>
| Local
| <code>gla</code>
| Proposed
| Glasgow area traffic.
|-
| <code>#perth</code>
| Local
| <code>per</code>
| Proposed
| Perth area traffic.
|-
| <code>#tayside</code>
| Regional
| <code>tay</code>
| Proposed
| Tayside traffic.
|-
| <code>#test</code>
| Wide
| Set the scope being tested
| Current
| Test messages. Use <code>sco</code>, <code>edi</code>, <code>gla</code>, or another scope that matches what you are testing.
|}

<blockquote>As of Summer 2026, The ScotMesh MC Mesh is still in its early growth phase. As such there is no pressing requirement to restrict in-country traffic to sub regions or local regions. In practical terms country wide traffic will not cause us any issues for at least another year, probably longer. So the country wide region <code>sco</code> will be enough until then.
</blockquote>
Proposed channels are shared names the community is still settling on. They are listed here so that people can talk about the same idea using the same name and scope, rather than ending up with several competing versions.

<span id="choosing-the-right-channel-in-the-future-2027-and-beyond"></span>
=== 🤔 Choosing the right channel in the future (2027 and beyond ===

Use the '''narrowest scope''' that still fits what you are sending. Examples:

<syntaxhighlight lang="text">#scotland / sco Scotland-wide mesh (Current)
#edinburgh / edi Local area (same idea for #glasgow/gla, #fife/fif, #dundee/dun, …)(Future)
#test / <scope> Pick the scope you are actually testing (current)
#ireland / ioi or sco Island of Ireland channel (pick scope for the path you want) (current)</syntaxhighlight>
<span id="good-practice-for-the-future-expanded-mesh"></span>
=== 👍 Good practice for the future expanded mesh ===

* Keep local traffic local where possible.
* Use <code>#test</code> for test messages so normal channels stay readable.
* Use Scotland-wide scope only when the conversation is relevant across Scotland.
* Use <code>ioi</code> when the message belongs on the Island of Ireland scope, or <code>sco</code> on <code>#ireland</code> when you want Scotland-wide scoped carriage (see [[MeshCore/Scopes|Scopes]]).
* Wildcard forwarding will remain disable in the Scottish setup.
* New public channel names tend to land better when discussed with the community first.
* Always check the Companion App scope before sending — a wrong scope and your message goes nowhere useful.

For more detail on setting scope in the Companion App, see [[MeshCore/Scopes|Scopes]]. For repeater and region code guidance, see [[MeshCore/Regions|Regions]]. For '''MQTT observers''' and map uplink, see [[MeshCore/Observers|Observers]].

MeshCore/Getting Started

2026-11-03T17:58:41Z

Admin: Condense connect steps; scope/hash now in main Settings; cleaner intro notes

{{DISPLAYTITLE:Getting Started}}
<span id="getting-started-within-scotmesh"></span>
== Getting Started within ScotMesh 🏴󠁧󠁢󠁳󠁣󠁴󠁿 ==

-----

<span id="what-is-scotmesh"></span>
=== 🏴󠁧󠁢󠁳󠁣󠁴󠁿 What is ScotMesh? ===

ScotMesh is community radio messaging networks across Scotland. It uses small, low-power LoRa radios to carry short messages between people — no mobile network, no Wi-Fi, no internet required.
Think of it like a local text messaging service that works off-grid, powered by volunteer-run repeaters dotted across the country.

<div class="sm-cx sm-cx-info">

ScotMesh runs both Meshtastic and MeshCore. This guide covers '''MeshCore'''.

</div>

Never used MeshCore before? Good — this is the place to start. No radio knowledge needed.

<div class="sm-cx sm-cx-info">

This guide is written for '''companion node''' devices — small LoRa radios that pair with the MeshCore Companion App on your phone. More capable standalone devices do exist, but those are out of scope for this guide. If you are setting one of those up, ask in the [https://discord.gg/ytxfyuDmSt Discord] for advice.
</div>
<span id="what-you-need"></span>
=== 🎒 What you need ===

* A MeshCore '''companion node''' — a small LoRa radio that pairs with your phone over Bluetooth.
* A smartphone — Android or iPhone both work.
* That is it.

<div class="sm-cx sm-cx-info">

Not sure which companion node to get? Ask in the [https://discord.gg/ytxfyuDmSt Discord] and the community can point you in the right direction.
</div>
<span id="get-the-app"></span>
=== 📱 1. Get the app ===

Download the '''MeshCore Companion App''' on your phone.

* '''Android:''' [https://play.google.com/store/search?q=meshcore MeshCore on Google Play]
* '''iPhone:''' [https://apps.apple.com/search?term=meshcore MeshCore on the App Store]

Open the app once it has installed.

<span id="flash-the-latest-firmware-to-the-lora-device"></span>
=== 👨‍💻 2. Flash the Latest Firmware to the LoRa Device ===

Before configuring the node, flash the LoRa device with the latest correct firmware for your exact hardware.

<blockquote>'''Important:''' Do '''not''' use the firmware that came pre-installed on the node.
</blockquote>
Pre-installed firmware may be outdated, built for a different board variant, or configured incorrectly for our mesh. Using the wrong firmware can cause connection issues, missing features, failed regional settings, or unreliable repeater behaviour.

Download the latest firmware from https://meshcore.io/, making sure you select the correct build for your exact device type, for example:

* RAK4631
* Heltec
* T114
* SenseCAP
* Waveshare
* Other supported hardware

After flashing, reboot the device and confirm the firmware version before continuing with the rest of the setup.

<span id="connect-your-device"></span>
=== 🔵 3. Connect your device ===

# Make sure your LoRa device is powered on.
# In the app, tap '''Add Device''' or the connect button.
# The app will search for nearby devices over Bluetooth. Select yours from the list.
# Wait a moment for it to connect. You should see your device appear in the app.

<div class="sm-cx sm-cx-info">

If the device does not show up, make sure Bluetooth is enabled on your phone and that the device is in pairing mode. Check your device’s instructions if you are unsure.
</div>
<span id="the-companion-node-settings"></span>
=== ⚙️ 3. The companion node settings ===

<div class="sm-cx sm-cx-info">

'''Regions''' split the mesh into geographic areas so traffic stays local and relevant, while agreed neighbours still interconnect. Your node's '''default scope''' is the region it uses for any traffic that has no scope of its own — which is why getting it right matters.

</div>
Before you can send anything from your companion app, you need to set it up for use in the ScotMesh MC mesh.

<span id="connecting-a-newly-flashed-companion-node-to-scotmesh"></span>
=== Connecting a Newly Flashed Companion Node to ScotMesh ===

After flashing the latest companion-node firmware, use the '''MeshCore app''' to connect to the node by Bluetooth and configure it for ScotMesh.

<ol style="list-style-type: decimal;">
<li>Power on the node, open the '''MeshCore app''', and connect to it over Bluetooth — on the connect screen, scan and select your node.</li>
<li>Confirm the firmware version shown is the latest correct build for your device, then give the node a clear, recognisable name so other ScotMesh users can spot it.</li>
<li>Open the node settings and set the radio region to '''UK/EU'''.</li>
<li>On the main '''Settings''' screen, set '''Default Scope''' to <code>sco</code> and '''Default Hash Size''' to <code>3 byte</code>. (Older app versions kept these under '''Experimental Settings'''.)</li>
<li>Save, reboot if prompted, then reconnect and check both settings are still set.</li>
<li>Open the ScotMesh channel and send a test message, for example <code>Test from my new ScotMesh node</code>, to confirm it sends.</li>
</ol>

Once these steps are complete, the companion node should be connected to ScotMesh and ready to send messages using the Scottish default scope.

<div class="sm-cx sm-cx-warning">

The default scope is the most important setting on ScotMesh. Without it, your messages may not travel anywhere useful on our network.
</div>
<span id="send-your-first-message-in-the-scotland-channel."></span>
=== 💬 4. Send your first message in the #scotland channel. ===

# In the app, open or create a channel called <code>#scotland</code>.
# Check the channel scope is set to <code>sco</code>. If the app shows a scope option, make sure it says <code>sco</code>.
# Type a short hello and send it.

That is all you need to do. If there is a repeater nearby, your message should travel through the mesh.

<span id="nothing-coming-back"></span>
=== 🤔 5. Nothing coming back? ===

Do not worry — this is normal at first.

* '''Check your scope.''' Go back to step 2 and confirm <code>sco</code> is set as the default and on the <code>#scotland</code> channel.
* '''Check repeater coverage.''' It is best '''NOT TO USE''' [https://map.meshcore.io/ MeshCore Node Map] to see if there are any repeaters near you. It is not up to date and can give false promise of coverage. Use the discover nearby nodes Scanner in the Meshcore app tools. > The web map is inaccurate and alway out of date. The companion app map will be empty until it hears adverts. the only way to reliably check for repeaters is to use the repeater search tool in the companion app
* '''Try <code>#test</code>.''' Send a message in a channel called <code>#test</code> with scope <code>sco</code> — this is what the community uses for testing. If someone else is active they may respond.
* '''Ask for help.''' The [https://discord.gg/ytxfyuDmSt Discord] is friendly and someone will help you work out what is happening.

<span id="where-to-go-next"></span>
=== 🗺️ Where to go next ===

Once you are up and running:

* [[MeshCore/Scopes|Scopes]] explains what scope means and how to set it properly for different channels.
* [[MeshCore/Channels|Channels]] lists the agreed community channels and what scope to use with each.
* [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]] is for you if you want to set up a repeater and help the network grow.

MeshCore/Channels

2026-11-03T17:54:26Z

Admin: Add #thenorf and #northeast channels (eng-ne)

{{DISPLAYTITLE:Channels}}
<span id="meshcore-channels-now-and-in-the-future"></span>
== MeshCore Channels (now and in the future) ==

Channels are where the conversation happens. Think of them like group chats — anyone with the right device and scope set can join in. There is nothing stopping you creating your own, but the ones below are the agreed community channels so everyone knows where to find each other.

In the Scottish MeshCore network, what really matters for routing is '''region scope''' — not the channel name. The channel name is for people; the scope is for the mesh.

<span id="channel-name-and-scope"></span>
=== 🏷️ Channel name and scope ===

A channel name and a region scope are related, but they are not the same thing.

For example:

<syntaxhighlight lang="text">Channel: #edinburgh
Scope: edi</syntaxhighlight>
The channel name is what you see. The scope is what tells the mesh to carry your message through Edinburgh-area repeaters.

<div class="sm-cx sm-cx-info">

Joining a channel does not automatically set the scope.

Before sending, check the channel settings in the Companion App and make sure the scope matches where you want the message to travel.
</div>
<span id="current-2026-and-proposed-2027-and-beyond-channels"></span>
=== 📡 Current (2026) and proposed (2027 and beyond) channels ===

The following table lists known community channels and proposed channels for Scotland.

'''Type is documentation only; it is not a Companion App setting'''. It groups channels by how you pick them: '''Wide''' for large-footprint traffic (whether the scope is <code>sco</code> or <code>ioi</code>), '''Regional''' for Scottish region area channels, and '''Local''' for Scottish City / town / metropolitan areas. Set '''Scope''' to match the reach you want.

{| class="wikitable"
|-
! Channel
! Type
! Scope
! Status
! Use
|-
| <code>#scotland</code>
| Wide
| <code>sco</code>
| Current
| General Scotland-wide MeshCore traffic.
|-
| <code>#ireland</code>
| Wide
| <code>ioi</code> or <code>sco</code>
| Current
| General Island of Ireland traffic.
|-
| <code>#norniron</code>
| Wide
| <code>ioi</code> or <code>sco</code>
| Current
| Northern Ireland Traffic
|-
| <code>#thenorf</code>
| Wide
| <code>eng-ne</code>
| Current
| North East England traffic.
|-
| <code>#northeast</code>
| Wide
| <code>eng-ne</code>
| Current
| North East England traffic.
|-
| <code>#central</code>
| Regional
| <code>cen</code>
| Proposed
| Central Scotland traffic.
|-
| <code>#dundee</code>
| Local
| <code>dun</code>
| Proposed
| Dundee area traffic.
|-
| <code>#edinburgh</code>
| Local
| <code>edi</code>
| Proposed
| Edinburgh area traffic.
|-
| <code>#falkirk</code>
| Local
| <code>fal</code>
| Proposed
| Falkirk area traffic.
|-
| <code>#fife</code>
| Regional
| <code>fif</code>
| Current
| Fife area traffic.
|-
| <code>#glasgow</code>
| Local
| <code>gla</code>
| Proposed
| Glasgow area traffic.
|-
| <code>#perth</code>
| Local
| <code>per</code>
| Proposed
| Perth area traffic.
|-
| <code>#tayside</code>
| Regional
| <code>tay</code>
| Proposed
| Tayside traffic.
|-
| <code>#test</code>
| Wide
| Set the scope being tested
| Current
| Test messages. Use <code>sco</code>, <code>edi</code>, <code>gla</code>, or another scope that matches what you are testing.
|}

<blockquote>As of Summer 2026, The ScotMesh MC Mesh is still in its early growth phase. As such there is no pressing requirement to restrict in-country traffic to sub regions or local regions. In practical terms country wide traffic will not cause us any issues for at least another year, probably longer. So the country wide region <code>sco</code> will be enough until then.
</blockquote>
Proposed channels are shared names the community is still settling on. They are listed here so that people can talk about the same idea using the same name and scope, rather than ending up with several competing versions.

<span id="choosing-the-right-channel-in-the-future-2027-and-beyond"></span>
=== 🤔 Choosing the right channel in the future (2027 and beyond ===

Use the '''narrowest scope''' that still fits what you are sending. Examples:

<syntaxhighlight lang="text">#scotland / sco Scotland-wide mesh (Current)
#edinburgh / edi Local area (same idea for #glasgow/gla, #fife/fif, #dundee/dun, …)(Future)
#test / <scope> Pick the scope you are actually testing (current)
#ireland / ioi or sco Island of Ireland channel (pick scope for the path you want) (current)</syntaxhighlight>
<span id="good-practice-for-the-future-expanded-mesh"></span>
=== 👍 Good practice for the future expanded mesh ===

* Keep local traffic local where possible.
* Use <code>#test</code> for test messages so normal channels stay readable.
* Use Scotland-wide scope only when the conversation is relevant across Scotland.
* Use <code>ioi</code> when the message belongs on the Island of Ireland scope, or <code>sco</code> on <code>#ireland</code> when you want Scotland-wide scoped carriage (see [[MeshCore/Scopes|Scopes]]).
* Wildcard forwarding will remain disable in the Scottish setup.
* New public channel names tend to land better when discussed with the community first.
* Always check the Companion App scope before sending — a wrong scope and your message goes nowhere useful.

For more detail on setting scope in the Companion App, see [[MeshCore/Scopes|Scopes]]. For repeater and region code guidance, see [[MeshCore/Regions|Regions]]. For '''MQTT observers''' and map uplink, see [[MeshCore/Observers|Observers]].

MeshCore/Repeater Quick Setup

2026-11-03T17:37:41Z

Admin: Tidy callout spacing (remove empty paragraph)

{{DISPLAYTITLE:Repeater Quick Setup}}
<span id="meshcore-repeater-quick-setup"></span>
== MeshCore Repeater Quick Setup ==

This is the short version for setting up a MeshCore repeater on ScotMesh.

A repeater helps the network by hearing MeshCore traffic and passing it on. A good repeater in a good location can make a big difference for everyone nearby.

<div class="sm-cx sm-cx-warning">

ScotMesh does not use wildcard forwarding.

Add the right regions, allow those regions, and deny wildcard forwarding with <code>region denyf *</code>.
</div>
<span id="quick-settings"></span>
=== Quick settings ===

{| class="wikitable"
|-
! Setting
! Use
|-
| Configurator
| MeshCore web flasher: <code>https://meshcore.io/flasher</code>
|-
| Preset
| UK / EU Narrow
|-
| Device role
| Repeater
|-
| Browser
| Chrome or Edge
|-
| Baseline regions
| <code>sco</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
|-
| Local regions
| Add only the areas the repeater genuinely serves
|-
| Wildcard forwarding
| Deny with <code>region denyf *</code>
|-
| Flood advert interval
| 24 hours
|-
| Path hash
| <code>set path.hash.mode 2</code> (3-byte, avoids collisions)
|-
| Double ACKs
| <code>set multi.acks 1</code>
|-
| Default scope
| <code>sco</code> — '''required''' so other repeaters accept your adverts
|}

<span id="before-you-start"></span>
=== Before you start ===

You will need:

* A supported LoRa device — open the [https://meshcore.io/flasher MeshCore Flasher] to see what can be flashed, or ask on [https://discord.gg/ytxfyuDmSt Discord].
* A USB data cable, not a charge-only cable.
* A laptop or desktop with Chrome or Edge.
* A sensible repeater location.
* Reliable power.

<div class="sm-cx sm-cx-info">

Location matters more than almost anything else.

A modest repeater in a high, clear spot is usually more useful than a powerful setup hidden indoors.
</div>
<span id="choose-your-region-settings"></span>
=== Choose your region settings ===

Start with the baseline <code>sco</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code> and <code>eng-ne</code>, then add the local areas the repeater genuinely covers.

{| class="wikitable"
|-
! Location / coverage
! Regions to add
! Notes
|-
| Any Scottish repeater
| <code>sco</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Baseline ScotMesh setup.
|-
| Fife
| <code>sco</code>, <code>fif</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Fife-wide coverage.
|-
| Central Scotland
| <code>sco</code>, <code>cen</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Wider Central belt coverage.
|-
| Falkirk
| <code>sco</code>, <code>cen</code>, <code>fal</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Falkirk local coverage.
|-
| Edinburgh area
| <code>sco</code>, <code>cen</code>, <code>edi</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Edinburgh-facing Central Scotland coverage.
|-
| Glasgow area
| <code>sco</code>, <code>cen</code>, <code>gla</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Glasgow-facing Central Scotland coverage.
|-
| Tayside
| <code>sco</code>, <code>tay</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Wider Tayside coverage.
|-
| Dundee area
| <code>sco</code>, <code>tay</code>, <code>dun</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Dundee local coverage.
|-
| Perth area
| <code>sco</code>, <code>tay</code>, <code>per</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Perth local coverage.
|-
| High site / bridge
| <code>sco</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>, plus genuinely served areas
| Do not add every region just because it is listed.
|}

<span id="simple-setup-flow"></span>
=== Simple setup flow ===

# Open the MeshCore web flasher in Chrome or Edge.
# Select your device.
# Choose the repeater role.
# Use the UK / EU Narrow preset.
# Flash the device with the latest stable firmware
# Set a clear repeater name.
# Add the right regions from the table above.
# Set flood adverts to 24 hours.
# Deny wildcard forwarding.
# Set <code>region default sco</code>.
# Save the region configuration.

<span id="simple-command-examples"></span>
=== Simple command examples ===

<span id="baseline-scottish-repeater"></span>
==== Baseline Scottish repeater ====

Use this when the repeater is part of ScotMesh but does not have a more specific local region yet.

<syntaxhighlight lang="text">region def sco|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

Without <code>region default sco</code>, your repeater’s adverts are sent unscoped. The Scottish network denies unscoped forwarding (<code>region denyf *</code>), so other repeaters will reject those adverts and will not know your repeater is there.
</div>
<span id="fife-repeater"></span>
==== Fife repeater ====

Use this when the repeater serves Fife.

<syntaxhighlight lang="text">region def sco fif|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<span id="central-scotland-falkirk-repeater"></span>
==== Central Scotland / Falkirk repeater ====

Use this when the repeater serves Falkirk and wider Central Scotland.

<syntaxhighlight lang="text">region def sco cen fal|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<span id="good-repeater-habits"></span>
=== Good repeater habits ===

* Put the repeater as high and clear as you reasonably can.
* Use stable power.
* Keep the antenna vertical.
* Give the repeater a name people can recognise.
* Add only the regions it genuinely serves.
* Use <code>region denyf *</code>; do not allow wildcard forwarding.
* Set <code>region default sco</code> so your adverts are accepted by the rest of the mesh.
* Set flood adverts to 24 hours.
* Ask the community before inventing new region codes.

<span id="where-to-go-next"></span>
=== Where to go next ===

* [[MeshCore/Regions|Regions]] has the fuller region guide and more command examples.
* [[MeshCore/Scopes|Scopes]] explains what Companion App users need to set.
* [[MeshCore/Channels|Channels]] lists the agreed and proposed channels.
* [https://docs.meshcore.io/cli_commands/ MeshCore CLI Commands] is the upstream command reference.

<span id="appendix-what-the-key-commands-mean"></span>
=== Appendix: what the key commands mean ===

{| class="wikitable"
|-
! Command
! Meaning
|-
| <code>region def sco …</code>
| Define the whole region tree in one line: the default scope first, then each code, with <code>name|*</code> resetting to the root.
|-
| <code>set multi.acks 1</code>
| Turn on double ACKs.
|-
| <code>set path.hash.mode 2</code>
| Use the 3-byte path hash (avoids collisions).
|-
| <code>region denyf *</code>
| Deny unscoped wildcard forwarding.
|-
| <code>set flood.advert.interval 24</code>
| Set flood adverts to 24 hours.
|-
| <code>region default sco</code>
| Set the default scope so adverts from this repeater are scoped to <code>sco</code> and accepted by the mesh.
|-
| <code>region save</code>
| Save the region configuration.
|}

MeshCore/Regions

2026-11-03T17:37:36Z

Admin: Tidy callout spacing (remove empty paragraph)

{{DISPLAYTITLE:Regions}}
<span id="meshcore-regions"></span>
== MeshCore Regions ==

-----

<div class="sm-cx sm-cx-info">

'''NOTE - A Regional Framework was impelemented in the ScotMesh Meshcore Mesh at the beginning of April 2026. This was out of sheer necessity as our mesh was dying under the flood traffic from England (24,000 flood packets & 600+ messages daily). This saved our mesh from descending into a chaotic, unusable mess of incoherent rambles and frustrated messaging failures. This is why an understaning of regions is imperative to understanding where we are today.'''
</div>

-----

This guide is for '''repeater owners'''.

The aim is simple: keep the scheme readable, predictable, and usable as the network grows.

<span id="why-regions-are-needed"></span>
=== Why regions are needed ===

MeshCore messages travel through repeaters for onward routing. Whilst this is the core function, if every repeater carries every message everywhere, the network becomes noisy, inefficient and flooded with uneccessary traffic.

Regions help us:

# '''Keep local traffic local''' — In the future, a message that only matters in one area wont always need to be repeated across every part of Scotland.
# '''Reduce unnecessary radio traffic''' — LoRa is subject to a finite airtime cycle per hour (compared with Wi-Fi or mobile data), so every avoidable repeat uses valuable airtime.
# '''Improve reliability''' — Less unnecessary repeating leaves more room for useful messages.
# '''Make planning clearer''' — Regions make repeater deployment easier to map, identify needs, plan future expansion and ease of ongoing mesh maintenance.
# '''Support controlled peering''' — Strategic repeaters can deliberately carry neighbouring traffic, such as the '''IOI peering agreement''' between Scotland and the Island of Ireland.

<span id="regions-and-scopes"></span>
=== Regions and scopes ===

There are two related concepts: '''regions''' and '''scopes'''.

{| class="wikitable"
|-
! Term
! Meaning
! Example
|-
| '''Region'''
| A label configured on a repeater to describe the area it serves.
| An Edinburgh-area repeater includes <code>edi</code>.
|-
| '''Scope'''
| A label applied to messages or channels to describe which area (or region) the traffic is intended to travel.
| The <code>#glasgow</code> channel might use <code>gla</code> when traffic should stay in that area.
|}

In a densely populated mesh, a repeater should only carry scoped traffic for regions it genuinely serves. In new or embryonic meshes, this requirment will be a future need but best practise planning mandates introducing regions as early as is practical.

<span id="wildcard-forwarding-is-not-allowed-see-info-box-at-top-of-this-document-for-context."></span>
=== Wildcard forwarding is not allowed (see info box at top of this document for context). ===

The wildcard marker is:

<syntaxhighlight lang="text">*</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

The important rule is: <code>*</code> will appear as a root parent in the region tree, but wildcard forwarding must be denied.

In other words, <code>region put sco *</code> is correct, but must be preceeded by <code>region denyf *</code> .
</div>
The Scottish MeshCore setup does not allow wildcard forwarding. Repeater owners must deny wildcard forwarding with:

<syntaxhighlight lang="text">region denyf *</syntaxhighlight>
You may still see <code>*</code> as the root parent when defining the region tree, for example <code>region put sco *</code>. That is different from allowing wildcard forwarding.

For channel names and suggested scopes, see [[MeshCore/Channels|Channels]].

<span id="scottish-region-code-approach"></span>
=== Scottish region code approach ===

For Scotland, we use simple three-letter lowercase codes.

We are not part of any UK wide mesh (for context see comment box at the top of this documnet) Therefore, '''we are not using any long prefixed names'''

We use short codes such as:

<syntaxhighlight lang="text">sco
cen
fal</syntaxhighlight>
Other countries and communities may use ISO-style hierarchical codes. That is valid for them, but the Scottish convention is designed to be short and easy to read in apps, analyser tools, and community discussions.

<span id="current-june-2026-agreed-region-codes"></span>
=== Agreed region codes ===

{| class="wikitable"
|-
! Code
! Area
|-
| <code>sco</code>
| Scotland — the default scope, carried by every Scottish repeater
|-
| <code>sco-admin</code>
| Scotland-only, for bots and utilities. Never peered out.
|-
| <code>cen</code>
| Central Scotland
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>gla</code>
| Glasgow area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>sti</code>
| Stirling area (proposed)
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>dun</code>
| Dundee area
|-
| <code>per</code>
| Perth area
|-
| <code>ioi</code>
| Island of Ireland — peering root beside <code>sco</code>
|-
| <code>wls</code>
| Wales — peering root beside <code>sco</code>
|-
| <code>eng-ne</code>
| North East England — peering root beside <code>sco</code>
|}

<span id="ioi-peering-agreement"></span>
=== IOI peering agreement ===

The Scottish and Irish MeshCore communities maintain a '''peering agreement''': scoped traffic is carried on the other network only where '''both''' sides configure for it.

Under that agreement, Scottish repeaters add the <code>ioi</code> region alongside <code>sco</code> where the Scottish baseline applies, and Island of Ireland repeaters add <code>sco</code> alongside their own region codes in the same spirit. Messages with matching '''scopes''' can then move between the two networks predictably, without relying on wildcard forwarding. For example channel names and typical scopes, see [[MeshCore/Channels|Channels]].

The <code>ioi</code> code is '''not''' a Scottish local region. It marks repeaters and traffic that deliberately participate in that peering.

Do not use:

<syntaxhighlight lang="text">ioi-sco</syntaxhighlight>
Use:

<syntaxhighlight lang="text">ioi</syntaxhighlight>
<span id="peering-with-scotland-other-regions"></span>
==== Peering with Scotland (other regions) ====

If another region wants to peer with Scotland in a similar way, they should already have the following in place:

# '''Wildcard flooding disallowed''' on their repeaters (the same principle as the Scottish setup: deny wildcard forwarding with <code>region denyf *</code>; see [[#wildcard-forwarding-is-not-allowed|Wildcard forwarding is not allowed]]).
# '''Appropriate regions on their repeaters''' so traffic is not forwarded wider than intended, and Scottish repeaters are not flooded with scoped traffic they did not agree to carry.
# '''Neighbouring Scotland in RF terms''' so equipment can '''directly''' peer, rather than assuming long unofficial relay chains.

When that fits your situation, contact the Scottish Mesh community on [https://discord.gg/ytxfyuDmSt Discord] so we can discuss scope names, boundaries, and a safe rollout.

<span id="recommended-hierarchy"></span>
=== Recommended hierarchy ===

Although the hierarchy is not written into the code itself, it can be thought of like this:

<syntaxhighlight lang="text">sco
cen
edi
gla
fal
sti (proposed)
fif
tay
dun
per
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
In plain English:

* <code>sco</code> is for Scotland-wide traffic, and <code>sco-admin</code> is a Scotland-only root for bots and utilities.
* <code>cen</code>, <code>tay</code>, and <code>fif</code> are Scottish sub regions.
* <code>edi</code>, <code>gla</code>, <code>fal</code>, <code>sti</code>, <code>dun</code> and <code>per</code> are local areas.
* <code>ioi</code> (Island of Ireland), <code>wls</code> (Wales) and <code>eng-ne</code> (North East England) are peering roots beside <code>sco</code>.

<span id="suggested-repeater-configuration-policy"></span>
=== Suggested repeater configuration policy ===

A Scottish repeater should normally be configured with:

# The country code <code>sco</code>, and <code>sco-admin</code> for Scotland-only utility traffic.
# The peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code>.
# The relevant regional code.
# The relevant local code, if appropriate.
# Any neighbouring codes that the repeater genuinely serves.

<div class="sm-cx sm-cx-warning">

Do not allow wildcard forwarding.

In command line interface (CLI) examples, this means using <code>region denyf *</code>
</div>
<span id="falkirk-central-scotland-repeater"></span>
==== Falkirk / Central Scotland repeater ====

A repeater covering the Falkirk area would usually have:

<syntaxhighlight lang="text">sco
cen
fal
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
<span id="edinburgh-facing-central-scotland-repeater"></span>
==== Edinburgh-facing Central Scotland repeater ====

A repeater that mainly serves Central Scotland but has strong coverage towards Edinburgh might use:

<syntaxhighlight lang="text">sco
cen
edi
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
<span id="fife-repeater"></span>
==== Fife repeater ====

A Fife repeater would usually have:

<syntaxhighlight lang="text">sco
fif
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
If it genuinely provides useful Central Scotland coverage, it may also include:

<syntaxhighlight lang="text">cen</syntaxhighlight>
<span id="scottish-repeaters-and-ioi"></span>
==== Scottish repeaters and <code>ioi</code> ====

Scottish repeaters carry the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> alongside <code>sco</code> and <code>sco-admin</code> — these are included in every repeater script:

<syntaxhighlight lang="text">sco
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
That keeps peering-capable forwarding available where the Scottish baseline is configured. It does not make <code>ioi</code> a Scottish local region.

<span id="good-practice-for-repeater-owners"></span>
=== Good practice for repeater owners ===

Use lowercase region codes. Do not use mixed case such as <code>SCO</code>, <code>Cen</code>, or <code>FAL</code>.

Use agreed codes. For example, use <code>edi</code> for the Edinburgh area, not <code>edn</code>, <code>edinburgh</code>, or <code>gb-edi</code>.

Add only the areas your repeater genuinely serves. A high-site repeater may reasonably serve several areas, but a repeater should not claim every region just because it can occasionally hear distant nodes.

Coordinate before adding new codes. If a new area needs a code, discuss it publicly before using it so that the community does not end up with competing names for the same place.

<span id="suggested-command-examples"></span>
=== Suggested command examples ===

The exact method may vary depending on firmware version and whether you are using the app, web configurator, USB serial, or remote administration. The upstream reference is the MeshCore [https://docs.meshcore.io/cli_commands/ CLI Commands] documentation, especially the region management commands.

<div class="sm-cx sm-cx-info">

New to repeater setup?

Start with [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]], then come back here for the fuller detail.
</div>
On current firmware (1.16+) the whole region tree goes in one <code>region def</code> line, followed by <code>region denyf *</code> and the standard <code>set</code> commands. The easiest way to get the exact script for your area is the [https://meshcore.scotmesh.net/repeater/ ScotMesh repeater builder]; the examples below show what it produces.

For a Central Scotland / Falkirk repeater:

<syntaxhighlight lang="text">region def sco cen fal|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
Then check the result with:

<syntaxhighlight lang="text">region</syntaxhighlight>
For a Tayside / Dundee repeater:

<syntaxhighlight lang="text">region def sco tay dun|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
For a Glasgow-area repeater:

<syntaxhighlight lang="text">region def sco cen gla|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
For a repeater that serves Scotland, Central Scotland, Glasgow, Edinburgh, and IOI peering (<code>ioi</code>):

<syntaxhighlight lang="text">region def sco cen|* gla|cen edi|cen sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

'''Set <code>region default sco</code> on your repeater.'''

Without a default scope, adverts sent by your repeater go out unscoped. Because the Scottish network uses <code>region denyf *</code>, other repeaters will reject those unscoped adverts and will never learn your repeater exists. Setting the default scope to <code>sco</code> ensures your adverts are carried normally across the mesh.
</div>
This is separate from flood forwarding permissions. For more detail, see [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

Always check for an <code>OK</code> response where applicable, and remember to save the configuration so it survives a reboot.

<span id="firmware-and-app-version-notes"></span>
=== Firmware and app version notes ===

Region and scope support depends on MeshCore firmware and app support.

Use the latest stable MeshCore firmware and app available for your device. Older firmware may still pass some traffic, but region management and scope handling may not behave as expected.

MeshCore region filtering was introduced across firmware and app releases, and default scope support was added later. The MeshCore posts [https://blog.meshcore.io/2026/01/20/region-filtering Region Filtering] and [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region] are useful background when checking version behaviour.

<span id="naming-and-publishing-new-region-codes"></span>
=== Naming and publishing new region codes ===

When a new Scottish area needs a code, use these rules:

# Use three lowercase letters.
# Make the code obvious to local users.
# Avoid clashing with existing agreed codes.
# Avoid overly small areas unless there is a real need.
# Discuss the code with the local MeshCore community before publishing it.

Examples of possible future codes might include:

<syntaxhighlight lang="text">sti = Stirling
liv = Livingston
abe = Aberdeen
inv = Inverness
ayr = Ayrshire
bor = Borders</syntaxhighlight>
These are examples only and should not be treated as agreed until the community confirms them.

<span id="common-questions"></span>
=== Common questions ===

<span id="do-regions-replace-normal-meshcore-messaging"></span>
==== Do regions replace normal MeshCore messaging? ====

No. Regions help control where scoped traffic is repeated.

<span id="should-every-scottish-repeater-have-sco-and-ioi"></span>
==== Should every Scottish repeater have the same baseline? ====

Yes. Every Scottish repeater carries <code>sco</code>, plus <code>sco-admin</code> and the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> — these are included in every repeater script.

<span id="should-every-repeater-have-every-scottish-region"></span>
==== Should every repeater have every Scottish region? ====

No. That would defeat the purpose of regions. Repeaters should only list the areas they genuinely serve.

<span id="should-we-use-gb-sco-instead-of-sco"></span>
==== Should we use <code>gb-sco</code> instead of <code>sco</code>? ====

Not for this Scottish scheme. Some wider UK or international guides use ISO-style codes, but the local Scottish agreement is to use short three-letter codes.

<span id="can-a-repeater-be-in-more-than-one-region"></span>
==== Can a repeater be in more than one region? ====

Yes. That is useful for high sites, border areas, or repeaters that genuinely link neighbouring areas.

<span id="can-we-allow-for-compatibility"></span>
==== Can we allow <code>*</code> for compatibility? ====

No. The Scottish MeshCore setup does not allow wildcard forwarding. Use the correct region scope instead.

<span id="summary"></span>
=== Summary ===

Regions give the Scottish MeshCore community a simple way to organise the network as it grows.

Our agreed approach is:

* Use three-letter lowercase codes.
* Use <code>sco</code> for Scotland.
* Carry <code>sco-admin</code> and the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> alongside <code>sco</code> on every repeater.
* Use <code>cen</code>, <code>tay</code>, <code>gla</code>, and <code>fif</code> for major regions where they match coverage.
* Use <code>fal</code>, <code>edi</code>, <code>gla</code>, <code>dun</code>, and <code>per</code> for local areas.
* Use <code>ioi</code> for Island of Ireland traffic under the IOI peering agreement.
* Deny wildcard forwarding with <code>region denyf *</code>.
* Do not use long prefixes such as <code>gb-sco</code> or <code>sco-fal</code> in this local scheme.

This gives us a clean, readable, and expandable foundation for building a coordinated Scottish MeshCore network.

MeshCore/Channels

2026-11-03T17:37:34Z

Admin: Tidy callout spacing (remove empty paragraph)

{{DISPLAYTITLE:Channels}}
<span id="meshcore-channels-now-and-in-the-future"></span>
== MeshCore Channels (now and in the future) ==

Channels are where the conversation happens. Think of them like group chats — anyone with the right device and scope set can join in. There is nothing stopping you creating your own, but the ones below are the agreed community channels so everyone knows where to find each other.

In the Scottish MeshCore network, what really matters for routing is '''region scope''' — not the channel name. The channel name is for people; the scope is for the mesh.

<span id="channel-name-and-scope"></span>
=== 🏷️ Channel name and scope ===

A channel name and a region scope are related, but they are not the same thing.

For example:

<syntaxhighlight lang="text">Channel: #edinburgh
Scope: edi</syntaxhighlight>
The channel name is what you see. The scope is what tells the mesh to carry your message through Edinburgh-area repeaters.

<div class="sm-cx sm-cx-info">

Joining a channel does not automatically set the scope.

Before sending, check the channel settings in the Companion App and make sure the scope matches where you want the message to travel.
</div>
<span id="current-2026-and-proposed-2027-and-beyond-channels"></span>
=== 📡 Current (2026) and proposed (2027 and beyond) channels ===

The following table lists known community channels and proposed channels for Scotland.

'''Type is documentation only; it is not a Companion App setting'''. It groups channels by how you pick them: '''Wide''' for large-footprint traffic (whether the scope is <code>sco</code> or <code>ioi</code>), '''Regional''' for Scottish region area channels, and '''Local''' for Scottish City / town / metropolitan areas. Set '''Scope''' to match the reach you want.

{| class="wikitable"
|-
! Channel
! Type
! Scope
! Status
! Use
|-
| <code>#scotland</code>
| Wide
| <code>sco</code>
| Current
| General Scotland-wide MeshCore traffic.
|-
| <code>#ireland</code>
| Wide
| <code>ioi</code> or <code>sco</code>
| Current
| General Island of Ireland traffic.
|-
| <code>#norniron</code>
| Wide
| <code>ioi</code> or <code>sco</code>
| Current
| Northern Ireland Traffic
|-
| <code>#central</code>
| Regional
| <code>cen</code>
| Proposed
| Central Scotland traffic.
|-
| <code>#dundee</code>
| Local
| <code>dun</code>
| Proposed
| Dundee area traffic.
|-
| <code>#edinburgh</code>
| Local
| <code>edi</code>
| Proposed
| Edinburgh area traffic.
|-
| <code>#falkirk</code>
| Local
| <code>fal</code>
| Proposed
| Falkirk area traffic.
|-
| <code>#fife</code>
| Regional
| <code>fif</code>
| Current
| Fife area traffic.
|-
| <code>#glasgow</code>
| Local
| <code>gla</code>
| Proposed
| Glasgow area traffic.
|-
| <code>#perth</code>
| Local
| <code>per</code>
| Proposed
| Perth area traffic.
|-
| <code>#tayside</code>
| Regional
| <code>tay</code>
| Proposed
| Tayside traffic.
|-
| <code>#test</code>
| Wide
| Set the scope being tested
| Current
| Test messages. Use <code>sco</code>, <code>edi</code>, <code>gla</code>, or another scope that matches what you are testing.
|}

<blockquote>As of Summer 2026, The ScotMesh MC Mesh is still in its early growth phase. As such there is no pressing requirement to restrict in-country traffic to sub regions or local regions. In practical terms country wide traffic will not cause us any issues for at least another year, probably longer. So the country wide region <code>sco</code> will be enough until then.
</blockquote>
Proposed channels are shared names the community is still settling on. They are listed here so that people can talk about the same idea using the same name and scope, rather than ending up with several competing versions.

<span id="choosing-the-right-channel-in-the-future-2027-and-beyond"></span>
=== 🤔 Choosing the right channel in the future (2027 and beyond ===

Use the '''narrowest scope''' that still fits what you are sending. Examples:

<syntaxhighlight lang="text">#scotland / sco Scotland-wide mesh (Current)
#edinburgh / edi Local area (same idea for #glasgow/gla, #fife/fif, #dundee/dun, …)(Future)
#test / <scope> Pick the scope you are actually testing (current)
#ireland / ioi or sco Island of Ireland channel (pick scope for the path you want) (current)</syntaxhighlight>
<span id="good-practice-for-the-future-expanded-mesh"></span>
=== 👍 Good practice for the future expanded mesh ===

* Keep local traffic local where possible.
* Use <code>#test</code> for test messages so normal channels stay readable.
* Use Scotland-wide scope only when the conversation is relevant across Scotland.
* Use <code>ioi</code> when the message belongs on the Island of Ireland scope, or <code>sco</code> on <code>#ireland</code> when you want Scotland-wide scoped carriage (see [[MeshCore/Scopes|Scopes]]).
* Wildcard forwarding will remain disable in the Scottish setup.
* New public channel names tend to land better when discussed with the community first.
* Always check the Companion App scope before sending — a wrong scope and your message goes nowhere useful.

For more detail on setting scope in the Companion App, see [[MeshCore/Scopes|Scopes]]. For repeater and region code guidance, see [[MeshCore/Regions|Regions]]. For '''MQTT observers''' and map uplink, see [[MeshCore/Observers|Observers]].

MeshCore/Scopes

2026-11-03T17:37:31Z

Admin: Tidy callout spacing (remove empty paragraph)

{{DISPLAYTITLE:Scopes}}
<span id="meshcore-scopes"></span>
== MeshCore Scopes ==

<div class="sm-cx sm-cx-success">

'''Quick start for most users:''' open the app, go to '''Experimental Settings''', set '''Default Scope Region''' to <code>sco</code>. That is all you need for normal Scottish traffic.
</div>
<div class="sm-cx sm-cx-warning">

'''Watch out:''' if you do not have a suitable '''scope''' set, repeaters on the Scottish MeshCore network wont forward your traffic. You can end up '''shouting into the void'''. Check your default scope and each channel’s scope before you count on messages reaching anyone.
</div>
Scope is the single setting that makes or breaks whether your messages go anywhere on ScotMesh. The channel name is for people — the scope is for the mesh. Set your '''default''' to <code>sco</code>, then adjust per channel when you need something narrower.

<div class="sm-cx sm-cx-info">

'''ScotMesh setup:''' Under '''Experimental Settings''', set the default scope region to <code>sco</code>, and keep <code>ioi</code> available in your scope list as well so you can pick it when you need it. For each channel, set scope to match '''where the traffic should travel'''—for example <code>#edinburgh</code> with <code>edi</code>. On '''<code>#ireland</code>''', you may use '''<code>ioi</code> or <code>sco</code>''': use <code>ioi</code> when the message should ride the Island of Ireland scoped path (IOI peering); use <code>sco</code> when you want the same channel but Scotland-wide scoped carriage on the mesh.
</div>
<span id="why-scope-matters"></span>
=== 🤷 Why scope matters ===

Without scope, repeaters have no way to know whether to carry your traffic. With it, messages travel through exactly the right part of the network.

* Keep Scottish traffic inside Scotland where appropriate.
* Allow controlled traffic to and from the Island of Ireland (IOI peering).
* Reduce unnecessary flooding.
* Keep the network easier to grow.

For example channel names and typical scopes, see [[MeshCore/Channels|Channels]]. For repeater region codes, see [[MeshCore/Regions|Regions]].

<span id="what-region-scope-means"></span>
=== 🗺️ What region scope means ===

Think of scope like a postcode on a letter — it tells the mesh where the message is meant to go.

<syntaxhighlight lang="text">sco = Scotland-wide
edi = Edinburgh area (example local)
ioi = Island of Ireland (IOI peering)</syntaxhighlight>
A message scoped to <code>sco</code> is forwarded by repeaters that carry <code>sco</code>as a region. A message scoped to <code>ioi</code> is forwarded by repeaters that carry <code>ioi</code>as a region. If scope is missing or wrong for your path, the message will go nowhere, it is dropped and ceases to exist.

<span id="wildcard-forwarding-is-not-allowed"></span>
=== 🚫 Wildcard forwarding is not allowed ===

The wildcard marker is <code>*</code>. Do not rely on it for routing — the Scottish MeshCore setup expects explicit region scopes.

In the '''Companion App''', your channel scope should always be a '''real region code''' (<code>sco</code>, <code>gla</code>, <code>ioi</code>, and so on). On '''repeaters''', CLI examples sometimes show <code>*</code> as the '''parent''' in a region tree (for example <code>region put sco *</code>); that is a different idea from wildcard '''forwarding''' and is covered in [[MeshCore/Regions|Regions]].

<span id="documented-scope-codes"></span>
=== 📋 Documented scope codes ===

{| class="wikitable"
|-
! Scope
! Typical use
|-
| <code>sco</code>
| Scotland-wide traffic
|-
| <code>sco-admin</code>
| Scotland-only, for bots and utilities (never peered out)
|-
| <code>cen</code>
| Central Scotland
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>gla</code>
| Glasgow area
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>sti</code>
| Stirling area
|-
| <code>per</code>
| Perth area
|-
| <code>dun</code>
| Dundee area
|-
| <code>ioi</code>
| Island of Ireland / IOI peering
|-
| <code>wls</code>
| Wales — peering
|-
| <code>eng-ne</code>
| North East England — peering
|}

For most day-to-day traffic in Scotland, '''<code>sco</code>''' is the right default. Use a '''local''' code when traffic should stay in that area, regardless of channel name.

<span id="default-scope-and-per-channel-scope"></span>
=== ⚙️ Default scope and per-channel scope ===

On ScotMesh, set your '''default''' scope region to <code>sco</code>. In the mobile app this is usually under '''Experimental Settings'''. Flood packets from the companion then use <code>sco</code> unless a '''group channel''' has its own scope.

'''Per-channel scope overrides the default.''' Examples:

* <code>#glasgow</code> with <code>gla</code> keeps traffic in the Glasgow-area part of the mesh.
* '''<code>#ireland</code> with <code>ioi</code>''' — message is scoped for the Island of Ireland path (IOI peering repeaters).
* '''<code>#ireland</code> with <code>sco</code>''' — same channel name, but the packet is Scotland-wide scoped; repeaters treat it like other <code>sco</code> traffic.

Keep both <code>sco</code> and <code>ioi</code> in your available scopes so you can switch. For background, see MeshCore [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

<span id="how-to-set-region-scope-in-the-companion-app"></span>
=== 📱 How to set region scope in the Companion App ===

Menus vary by app version and platform; the usual flow is:

<syntaxhighlight lang="text">1. Open the MeshCore Companion App
2. Open the channel you want to use
3. Open the channel options or channel menu
4. Find the region scope option
5. Select or add the region code you need
6. Send with that scope active</syntaxhighlight>
Often the channel menu includes something like '''Set Region Scope''', then you pick or type the code (for example <code>sco</code>, <code>edi</code>, or <code>ioi</code>).

<span id="examples"></span>
=== 💬 Examples ===

'''Scotland-wide'''

<syntaxhighlight lang="text">Channel: #scotland
Scope: sco</syntaxhighlight>
'''Local (example)'''

<syntaxhighlight lang="text">Channel: #glasgow
Scope: gla</syntaxhighlight>
'''<code>#ireland</code> with Island of Ireland scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope: ioi</syntaxhighlight>
'''<code>#ireland</code> with Scotland-wide scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope: sco</syntaxhighlight>
The channel name does not set scope by itself — you still choose <code>ioi</code> or <code>sco</code> (or another code) in the channel settings.

<span id="quick-choices"></span>
=== ⚡ Quick choices ===

* Normal Scottish chat: default <code>sco</code>, or <code>#scotland</code> with <code>sco</code>.
* Local-only: local scope such as <code>edi</code> or <code>gla</code> when traffic should stay in that area.
* '''<code>#ireland</code>:''' <code>ioi</code> for IOI-scoped path, '''<code>sco</code>''' when you want Scotland-wide scoped carriage on that channel.
* Tests: <code>#test</code> with whichever scope you are testing (<code>tay</code>, <code>sco</code>, …).

If you are unsure, '''<code>sco</code>''' is the safe general default for Scottish-side traffic.

<span id="what-to-avoid"></span>
=== ❌ What to avoid ===

* Sending traffic with no region scope.
* Relying on wildcard forwarding.
* Assuming the channel name alone chooses routing.

<span id="summary"></span>
=== 📝 Summary ===

<syntaxhighlight lang="text">Default: sco on ScotMesh
Override per channel when needed
#ireland: ioi OR sco
Local: use the local code when traffic should stay local
Check your companion app is scoped before you send your initial messages</syntaxhighlight>
Getting scope right keeps mesh traffic logical and the mesh relaible, easier to use and simpler to grow.

MeshCore/Getting Started

2026-11-03T17:37:31Z

Admin: Tidy callout spacing (remove empty paragraph)

{{DISPLAYTITLE:Getting Started}}
<span id="getting-started-within-scotmesh"></span>
== Getting Started within ScotMesh 🏴󠁧󠁢󠁳󠁣󠁴󠁿 ==

-----

<span id="what-is-scotmesh"></span>
=== 🏴󠁧󠁢󠁳󠁣󠁴󠁿 What is ScotMesh? ===

ScotMesh is community radio messaging networks across Scotland. It uses small, low-power LoRa radios to carry short messages between people — no mobile network, no Wi-Fi, no internet required.
Think of it like a local text messaging service that works off-grid, powered by volunteer-run repeaters dotted across the country.

'''Currently both Meshtastic and Mescore networks are available'''

<span id="note-this-document-focuses-on-meschore"></span>
== '''NOTE This document focuses on Meschore''' ==

Never used MeshCore before? Good — this is the place to start. No radio knowledge needed.

<div class="sm-cx sm-cx-info">

This guide is written for '''companion node''' devices — small LoRa radios that pair with the MeshCore Companion App on your phone. More capable standalone devices do exist, but those are out of scope for this guide. If you are setting one of those up, ask in the [https://discord.gg/ytxfyuDmSt Discord] for advice.
</div>
<span id="what-you-need"></span>
=== 🎒 What you need ===

* A MeshCore '''companion node''' — a small LoRa radio that pairs with your phone over Bluetooth.
* A smartphone — Android or iPhone both work.
* That is it.

<div class="sm-cx sm-cx-info">

Not sure which companion node to get? Ask in the [https://discord.gg/ytxfyuDmSt Discord] and the community can point you in the right direction.
</div>
<span id="get-the-app"></span>
=== 📱 1. Get the app ===

Download the '''MeshCore Companion App''' on your phone.

* '''Android:''' [https://play.google.com/store/search?q=meshcore MeshCore on Google Play]
* '''iPhone:''' [https://apps.apple.com/search?term=meshcore MeshCore on the App Store]

Open the app once it has installed.

<span id="flash-the-latest-firmware-to-the-lora-device"></span>
=== 👨‍💻 2. Flash the Latest Firmware to the LoRa Device ===

Before configuring the node, flash the LoRa device with the latest correct firmware for your exact hardware.

<blockquote>'''Important:''' Do '''not''' use the firmware that came pre-installed on the node.
</blockquote>
Pre-installed firmware may be outdated, built for a different board variant, or configured incorrectly for our mesh. Using the wrong firmware can cause connection issues, missing features, failed regional settings, or unreliable repeater behaviour.

Download the latest firmware from https://meshcore.io/, making sure you select the correct build for your exact device type, for example:

* RAK4631
* Heltec
* T114
* SenseCAP
* Waveshare
* Other supported hardware

After flashing, reboot the device and confirm the firmware version before continuing with the rest of the setup.

<span id="connect-your-device"></span>
=== 🔵 3. Connect your device ===

# Make sure your LoRa device is powered on.
# In the app, tap '''Add Device''' or the connect button.
# The app will search for nearby devices over Bluetooth. Select yours from the list.
# Wait a moment for it to connect. You should see your device appear in the app.

<div class="sm-cx sm-cx-info">

If the device does not show up, make sure Bluetooth is enabled on your phone and that the device is in pairing mode. Check your device’s instructions if you are unsure.
</div>
<span id="the-companion-node-settings"></span>
=== ⚙️ 3. The companion node settings ===

<blockquote>For these settings, understanding the regional framework is important because it defines how traffic is organised and routed across the mesh. Regions (set on repeater nodes) allow the wider mesh to be split into sensible geographic areas, helping messages, adverts, and repeater traffic stay relevant to the area they are intended for while still allowing agreed neighbouring regions to interconnect where required. Setting the '''default scope''' tells the node which region it should use automatically when sending or repeating traffic that does not already have a specific scope applied. In practice, this helps keep local traffic local, reduces unnecessary flooding across unrelated areas, and improves the reliability and manageability of the mesh.
</blockquote>
Before you can send anything from your companion app, you need to set it up for use in the ScotMesh MC mesh.

<span id="connecting-a-newly-flashed-companion-node-to-scotmesh"></span>
=== Connecting a Newly Flashed Companion Node to ScotMesh ===

After flashing the latest companion-node firmware, use the '''MeshCore app''' to connect to the node by Bluetooth and configure it for ScotMesh.

<ol style="list-style-type: decimal;">
<li><p>Power on the newly flashed companion node.</p></li>
<li><p>Open the '''MeshCore app''' on your phone.</p></li>
<li><p>Make sure Bluetooth is enabled on your phone.</p></li>
<li><p>In the MeshCore app, go to the Bluetooth connection screen.</p></li>
<li><p>Scan for nearby Bluetooth MeshCore devices.</p></li>
<li><p>Select your newly flashed companion node from the list.</p></li>
<li><p>Wait for the app to connect to the node.</p></li>
<li><p>Confirm the node shows as connected in the MeshCore app.</p></li>
<li><p>Check the firmware version shown in the app and confirm it is the latest correct firmware for your device.</p></li>
<li><p>Give the node a clear and recognisable name so other ScotMesh users can identify it.</p></li>
<li><p>Open the node settings in the MeshCore app.</p></li>
<li><p>Set the LoRa/radio region to the correct UK/EU setting.</p></li>
<li><p>Open '''Experimental Settings''' and set the following:</p>
<ul>
<li>'''Default Scope:''' <code>sco</code></li>
<li>'''Default Hash Size:''' <code>3 byte</code></li></ul>
</li>
<li><p>Save or apply the settings.</p></li>
<li><p>Reboot the companion node if the app asks you to do so.</p></li>
<li><p>Reconnect to the companion node by Bluetooth after it restarts.</p></li>
<li><p>Confirm the '''Default Scope''' is still set to <code>sco</code>.</p></li>
<li><p>Confirm the '''Default Hash Size''' is still set to <code>3 byte</code>.</p></li>
<li><p>Open the ScotMesh public channel.</p></li>
<li><p>Send a short test message, for example:</p>
<p><code>Test from newly configured ScotMesh companion node</code></p></li>
<li><p>Confirm that the message sends successfully.</p></li></ol>

Once these steps are complete, the companion node should be connected to ScotMesh and ready to send messages using the Scottish default scope.

<div class="sm-cx sm-cx-warning">

The default scope is the most important setting on ScotMesh. Without it, your messages may not travel anywhere useful on our network.
</div>
<span id="send-your-first-message-in-the-scotland-channel."></span>
=== 💬 4. Send your first message in the #scotland channel. ===

# In the app, open or create a channel called <code>#scotland</code>.
# Check the channel scope is set to <code>sco</code>. If the app shows a scope option, make sure it says <code>sco</code>.
# Type a short hello and send it.

That is all you need to do. If there is a repeater nearby, your message should travel through the mesh.

<span id="nothing-coming-back"></span>
=== 🤔 5. Nothing coming back? ===

Do not worry — this is normal at first.

* '''Check your scope.''' Go back to step 2 and confirm <code>sco</code> is set as the default and on the <code>#scotland</code> channel.
* '''Check repeater coverage.''' It is best '''NOT TO USE''' [https://map.meshcore.io/ MeshCore Node Map] to see if there are any repeaters near you. It is not up to date and can give false promise of coverage. Use the discover nearby nodes Scanner in the Meshcore app tools. > The web map is inaccurate and alway out of date. The companion app map will be empty until it hears adverts. the only way to reliably check for repeaters is to use the repeater search tool in the companion app
* '''Try <code>#test</code>.''' Send a message in a channel called <code>#test</code> with scope <code>sco</code> — this is what the community uses for testing. If someone else is active they may respond.
* '''Ask for help.''' The [https://discord.gg/ytxfyuDmSt Discord] is friendly and someone will help you work out what is happening.

<span id="where-to-go-next"></span>
=== 🗺️ Where to go next ===

Once you are up and running:

* [[MeshCore/Scopes|Scopes]] explains what scope means and how to set it properly for different channels.
* [[MeshCore/Channels|Channels]] lists the agreed community channels and what scope to use with each.
* [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]] is for you if you want to set up a repeater and help the network grow.

MeshCore

2026-11-03T17:37:30Z

Admin: Tidy callout spacing (remove empty paragraph)

[[File:ScotMesh-meshcore-lockup.svg|link=|alt=ScotMesh MeshCore|240px|class=mc-pagelogo]]

<span id="meshes"></span>
== Meshes ==

ScotMesh has both Meshtastic and MeshCore — radio messaging systems for small LoRa devices. It lets people send short messages across a volunteer-run network without needing mobile coverage, Wi-Fi, or the internet. Carry a small companion node in your pocket, connect it to your phone, and you’re on the mesh.

<span id="the-remainder-of-this-document-focuses-on-meshcore."></span>
== The remainder of this document focuses on Meshcore. ==

<span id="key-ideas"></span>
=== 💡 Key ideas ===

{| class="wikitable"
|-
! Term
! Meaning
|-
| '''Channel'''
| A named place for conversation, such as <code>#scotland</code>, <code>#glasgow</code>, or <code>#ireland</code>.
|-
| '''Scope'''
| The region code applied to messages in a channel, such as <code>sco</code>, <code>gla</code>, or <code>ioi</code>.
|-
| '''Region'''
| A code configured on a repeater to describe the area it serves.
|-
| '''Repeater'''
| A fixed node that hears MeshCore traffic and repeats it to extend coverage.
|}

<span id="new-to-scotmesh"></span>
=== 👋 New to ScotMesh? ===

* [[MeshCore/Getting Started|Getting Started]] — what it is, what you need, your first message.
* [[MeshCore/Scopes|Scopes]] — the one setting that matters most.
* [[MeshCore/Channels|Channels]] — where to talk and what scope to use.
* [[MeshCore/FAQ|FAQ]] — quick answers to common questions.

<span id="setting-up-a-repeater"></span>
=== 📡 Setting up a repeater? ===

* [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]] — start here for hardware and commands.
* [[MeshCore/Regions|Regions]] — full region code reference and configuration policy.
* [[MeshCore/Observers|Observers]] — MQTT map uplink setup.

<span id="interested-in-the-technical-detail"></span>
=== 🔧 Interested in the technical detail? ===

* [https://blog.meshcore.io/2026/01/20/region-filtering Region Filtering]
* [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region]
* [https://docs.meshcore.io/cli_commands/ CLI Commands]

-----

<div class="sm-cx sm-cx-warning">

'''ScotMesh network policy:''' wildcard <code>*</code> forwarding is not allowed. Companion App users should set their default region scope to <code>sco</code> under '''Experimental Settings'''. Repeater owners should use <code>region denyf *</code>. See [[MeshCore/Regions|Regions]] for detail.
</div>

MediaWiki:Common.css

2026-11-03T17:37:28Z

Admin: Fix callout box empty-paragraph spacing

/* ScotMesh content styles. Core brand (colours/fonts/cards) is render-blocking in LocalSettings. */
.sm-cx{border-radius:6px;padding:.75rem 1.1rem;margin:1.1rem 0;border-left:4px solid #22324D;background:#101C30}
.sm-cx-info{border-left-color:#005EB8}
.sm-cx-warning{border-left-color:#F2B33D}
.sm-cx-success{border-left-color:#65C281}
.sm-cx > :first-child{margin-top:0}
.sm-cx > :last-child{margin-bottom:0}
.sm-cx p{margin:.5rem 0}
/* network lockup at the top of a network section page */
.mc-pagelogo{display:block;margin:.2rem 0 1.3rem}
.mc-pagelogo img,.mc-pagelogo .mw-file-element{width:min(240px,62%);height:auto}
/* front-page community join (legacy, still used on Main Page note) */
.sm-join-note{display:block;font-family:"IBM Plex Mono",ui-monospace,monospace;font-size:.82rem;color:#8FA2BD;margin:.2rem 0 0}
.sm-join-note code{color:#E6EDF7;background:#0C1729;border:1px solid #22324D;padding:.05rem .4rem;border-radius:3px}

MeshCore/MeshMapper-Friendly Repeaters

2026-11-03T17:27:24Z

Admin: Normalise preset label to UK / EU Narrow

{{DISPLAYTITLE:MeshMapper-Friendly Repeaters}}
<span id="meshmapper-friendly-repeater-configuration-spec-for-scotmesh-meshcore"></span>
== MeshMapper-Friendly Repeater Configuration Spec for Scotmesh MeshCore ==

These are guidelines for a uniform configuration of repeaters taking part in '''Scotmesh MeshCore'''.

These are not hard and fast rules, but certain specifications are necessary for smooth MeshMapper reporting. Using these settings will help ensure a smooth-running mesh.

-----

<span id="identification"></span>
=== Identification ===

Use '''ASCII characters only''' for the repeater name.

This makes MeshMapper management much easier, as most emoji characters are '''not''' read by MeshMapper.

You can use a single emoji to customise your MeshCore app icon on your companion radio, but this has no effect on the repeater name as seen by MeshMapper.

-----

<span id="location"></span>
=== Location ===

Repeater location should be set as accurately as possible, while still protecting the safety and security of the repeater site.

For example, setting the repeater location around '''200 metres''' from the real location gives a search area of approximately '''12.6 hectares'''. This would take a careful walking search of around '''8 hours''' to cover.

Setting the location '''200–250 metres away''' from the real position gives a useful level of obfuscation while still allowing the repeater to appear correctly on MeshMapper.

If no location is set:

* The repeater will be excluded from MeshMapper
* You will not see useful telemetry, such as zero-hop neighbours
* Routing path analysis, enhancements and other mesh planning will not be possible

-----

<span id="basic-owner-information"></span>
=== Basic Owner Information ===

Please ensure basic owner information is set.

-----

<span id="advert-settings"></span>
=== Advert Settings ===

Recommended settings:

* '''Zero-hop advert:''' 60–120 minutes
* '''Flood advert:''' 24 hours

-----

<span id="radio-settings"></span>
=== Radio Settings ===

Please use:

* '''UK / EU Narrow'''
* '''Frequency:''' 869.618 MHz
* '''Spreading Factor:''' SF8
* '''Coding Rate:''' CR8
* '''Bandwidth:''' 62.5 kHz

Recommended CLI settings:

<syntaxhighlight lang="text">set multi.acks 1
set path.hash.mode 2</syntaxhighlight>
This enables:

* '''Multi ACKs'''
* '''3-byte path hash'''

Please keep your repeater updated with the latest firmware whenever possible.

Please also ensure your companion radio or radios are set to:

* '''Double ACKs on'''
* '''3-byte path hash'''

-----

<span id="access"></span>
=== Access ===

Do not leave the guest login with no password.

For continuity, please set the guest password to:

<syntaxhighlight lang="text">hello</syntaxhighlight>
This gives at least some security over the guest login.

Keep your admin password safe.

-----

<span id="region-scope"></span>
=== Region / Scope ===

Please set both the '''default scope''' and '''home scope''' to:

<syntaxhighlight lang="text">sco</syntaxhighlight>
Please also deny flood to:

<syntaxhighlight lang="text">*</syntaxhighlight>
Channels set to region <code>sco</code> are:

* <code>Public</code>
* <code>#scotland</code>

Optionally, you may also add the channel:

<syntaxhighlight lang="text">#ireland</syntaxhighlight>
with region:

<syntaxhighlight lang="text">ioi</syntaxhighlight>
Scotland and the Island of Ireland have collaborated very well to construct a civilised MeshCore environment.

As Scotmesh expands, we may add nested sub-regions within <code>sco</code>.

-----

<span id="time-setting-and-synchronisation-with-meshmapper"></span>
=== Time Setting and Synchronisation with MeshMapper ===

After power-up of the repeater, the time is always incorrect.

Please use the following procedure to set the correct time and synchronise it with MeshMapper.

This process assumes you have already configured the repeater for use.

<span id="phone-app-method"></span>
==== Phone App Method ====

# Open the settings page in the phone app.
# Perform the usual '''Sync Clock''' action.
# Scroll to the bottom of the page.
# Tap '''Reboot'''.

Unlike pressing the physical '''reset''' button on the repeater board, this is a '''soft reset'''.

A soft reset does '''not''' reset the clock, but it appears to be important for finalising certain settings.

For reference:

* Pressing '''Reboot''' in the app is a '''soft reset'''
* Pressing the physical reset button on the board is a '''hard reset'''
* A hard reset resets all settings not stored in flash

You may also use CLI commands to perform the same task if preferred.

-----

<span id="closing-note"></span>
=== Closing Note ===

I hope this helps with the ease of configuration.

This guide assumes you already understand the menu and command structure of MeshCore repeaters, devices and apps.

If there is a menu item you cannot find, ask on the Discord server and one of the admins or knowledgeable users will help you along.ur content here

Meshtastic

2026-11-03T17:25:56Z

Admin: Add scotmesh/meshtastic lockup to landing

[[File:ScotMesh-meshtastic-lockup.svg|link=|alt=ScotMesh Meshtastic|240px|class=mc-pagelogo]]

{{DISPLAYTITLE:Meshtastic}}
'"'"'ScotMesh Meshtastic'"'"' — documentation for the ScotMesh Meshtastic network.

<div class="sm-tagline">Section layout · content migration in progress</div>

Introduction and setup guides coming over from the old wiki.

MeshCore/FAQ

2026-11-03T17:21:58Z

Admin: Improve rendering + apply freshness fixes (regions/scopes/CLI to current)

{{DISPLAYTITLE:FAQ}}
<span id="meshcore-faq"></span>
== MeshCore FAQ 🙋 ==

Quick answers to the questions that come up most often. If yours is not here, ask on [https://discord.gg/ytxfyuDmSt Discord].

-----

<span id="do-i-need-a-radio-licence-to-use-meshcore"></span>
=== Do I need a radio licence to use meshcore? ===

No. MeshCore uses licence-exempt LoRa frequencies (868 MHz in the UK). Anyone can carry a companion node and use the app. No amateur radio licence required.

-----

<span id="what-is-the-range"></span>
=== What is the range? ===

It depends heavily on where you are and whether there is a repeater nearby. A companion node in the open might reach a couple of kilometres to a nearby repeater. A well-sited repeater on a hill can cover tens of kilometres. In a city with buildings in the way, range is shorter.

Currently our distance record across water is '''160km from Galloway to Dublin.'''

Our record across land is '''120km from Angus down to SOuth Lanark.'''

-----

<span id="why-cant-i-hear-anyone"></span>
=== Why can’t I hear anyone? ===

A few things to check, in order:

# '''Scope is wrong.''' The most common cause. Go to '''Experimental Settings''' in the app and confirm '''Default Scope Region''' is set to <code>sco</code>. Then check the channel scope too — see [[MeshCore/Scopes|Scopes]].
# '''No repeater nearby.''' Use '''Tools → Repeater Scanner''' in the MeshCore app to scan for nearby ScotMesh repeaters, then wait for the scan to complete and confirm that local repeaters are being discovered.
# '''Wrong radio preset.''' Make sure your device is flashed with the '''UK / EU Narrow''' preset. A device on the wrong channel or spreading factor will not hear anything.
# '''Device not transmitting.''' Try <code>#test</code> with scope <code>sco</code> — you should at least see your own message go out.

If you have checked all of the above and still hear nothing, ask on [https://discord.gg/ytxfyuDmSt Discord].

-----

<span id="what-is-the-difference-between-a-channel-and-a-scope"></span>
=== What is the difference between a channel and a scope? ===

* A '''channel''' is a named group chat — <code>#scotland</code>, <code>#glasgow</code>, <code>#test</code>. It is just a label for people.
* A '''scope''' is a region code that repeaters use to decide whether to carry your message — <code>sco</code>, <code>gla</code>, <code>edi</code>.

You can send a message on <code>#glasgow</code> with the scope set to <code>sco</code> and it will go Scotland-wide. Or you can set the scope to <code>gla</code> and it will only travel through Glasgow-area repeaters. The channel name does not change that — the scope does. See [[MeshCore/Scopes|Scopes]] for the full explanation.

-----

<span id="why-is-the-wildcard-not-allowed"></span>
=== Why is the <code>*</code> wildcard not allowed? ===

The <code>*</code> wildcard tells repeaters to forward everything to everyone. On a well-grown network that floods the airtime with traffic that most people do not need. ScotMesh uses deliberate region scopes instead — set <code>sco</code> for Scotland-wide, <code>gla</code> for Glasgow, and so on — so traffic only travels where it is actually useful.

<blockquote>In late March / early April 2026, the ScotMesh MC network officially formed when West Coast repeaters successfully linked with East Coast repeaters. This gave us around two weeks of reliable country-wide messaging across Scotland, proving that the network could work well as a connected Scottish mesh.The situation changed when our Galloway repeater linked us into Ireland and, through that path, to the remainder of the wider UK mesh. While wider interconnection may sound positive, in practice it created a major problem for ScotMesh. The network was suddenly exposed to a very high level of uncontrolled flood traffic, estimated at around 24,000 flood packets per day, plus around 600 public messages being present. Much of this traffic was unnecessary for Scottish users and included political arguments, off-topic content, and various abusive or inappropriate remarks.
This level of uncontrolled traffic had a damaging effect on ScotMesh. It increased congestion, reduced the reliability of useful local messaging, and made the network harder to manage. This was the reason ScotMesh moved towards a clearer regional framework, allowing Scotland to remain connected where appropriate while keeping routine traffic scoped, relevant, and manageable. This is also the reason why are unlikely to ever allow wildcard flooding again.
</blockquote>
There is one exception: <code>*</code> is used as a root parent in repeater configuration commands (for example <code>region put sco *</code>). That is a region tree concept, not wildcard forwarding. See [[MeshCore/Regions|Regions]] for the detail.

-----

<span id="can-i-use-scotmesh-without-a-repeater-nearby"></span>
=== Can I use ScotMesh without a repeater nearby? ===

Yes, but your range is very limited. Two companion nodes in line of sight can talk directly. If there is no repeater between you and another user, messages will only reach as far as direct radio range allows — often just a few hundred metres in built-up areas.

If you want to extend coverage in your area, the best thing to do is put up a repeater. See [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]].

-----

<span id="what-device-should-i-buy"></span>
=== What device should I buy? ===

The [https://meshcore.io/flasher MeshCore Flasher] lists devices that can be flashed with MeshCore firmware — that is a good starting point for what is currently supported. Popular choices include boards from Heltec, LilyGo, and RAK, but the community’s preferences do shift as new hardware comes out.

The best thing to do is ask on [https://discord.gg/ytxfyuDmSt Discord] — someone will point you at whatever is working well right now.

-----

<span id="how-do-i-know-if-my-device-is-working"></span>
=== How do I know if my device is working? ===

Send a message on <code>#test</code> with scope <code>sco</code>. If you can see the message appear in the app after sending, the device is transmitting. If someone else on the network responds, you have confirmed two-way comms.

Use '''Tools → Repeater Scanner''' in the MeshCore app to scan for nearby ScotMesh repeaters, then wait for the scan to complete and confirm that local repeaters are being discovered.

-----

<span id="do-i-need-to-set-scope-for-every-channel-separately"></span>
=== Do I need to set scope for every channel separately? ===

Not necessarily. If you set a '''default scope''' of <code>sco</code> in Experimental Settings, that applies to any channel that does not have its own scope override. You only need to set a per-channel scope when you want something different — for example <code>gla</code> on <code>#glasgow</code> to keep traffic local, or <code>ioi</code> on <code>#ireland</code> for the Island of Ireland path. See [[MeshCore/Scopes|Scopes]] for the full detail.

-----

<span id="what-is-the-island-of-ireland-ioi-scope"></span>
=== What is the Island of Ireland (<code>ioi</code>) scope? ===

ScotMesh and the Irish MeshCore community have a peering agreement. Repeaters on both sides carry the <code>ioi</code> scope so that traffic can move between the two networks in a controlled way — without flooding everything. You can join <code>#ireland</code> and set scope to <code>ioi</code> to talk on that path. See [[MeshCore/Channels|Channels]] for more.

-----

<span id="something-else-not-answered-here"></span>
=== Something else not answered here? ===

Jump on [https://discord.gg/ytxfyuDmSt Discord] — the community is friendly and happy to help.

MeshCore/Repeater Quick Setup

2026-11-03T17:21:53Z

Admin: Improve rendering + apply freshness fixes (regions/scopes/CLI to current)

{{DISPLAYTITLE:Repeater Quick Setup}}
<span id="meshcore-repeater-quick-setup"></span>
== MeshCore Repeater Quick Setup ==

This is the short version for setting up a MeshCore repeater on ScotMesh.

A repeater helps the network by hearing MeshCore traffic and passing it on. A good repeater in a good location can make a big difference for everyone nearby.

<div class="sm-cx sm-cx-warning">

ScotMesh does not use wildcard forwarding.

Add the right regions, allow those regions, and deny wildcard forwarding with <code>region denyf *</code>.

</div>
<span id="quick-settings"></span>
=== Quick settings ===

{| class="wikitable"
|-
! Setting
! Use
|-
| Configurator
| MeshCore web flasher: <code>https://meshcore.io/flasher</code>
|-
| Preset
| UK / EU Narrow
|-
| Device role
| Repeater
|-
| Browser
| Chrome or Edge
|-
| Baseline regions
| <code>sco</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
|-
| Local regions
| Add only the areas the repeater genuinely serves
|-
| Wildcard forwarding
| Deny with <code>region denyf *</code>
|-
| Flood advert interval
| 24 hours
|-
| Path hash
| <code>set path.hash.mode 2</code> (3-byte, avoids collisions)
|-
| Double ACKs
| <code>set multi.acks 1</code>
|-
| Default scope
| <code>sco</code> — '''required''' so other repeaters accept your adverts
|}

<span id="before-you-start"></span>
=== Before you start ===

You will need:

* A supported LoRa device — open the [https://meshcore.io/flasher MeshCore Flasher] to see what can be flashed, or ask on [https://discord.gg/ytxfyuDmSt Discord].
* A USB data cable, not a charge-only cable.
* A laptop or desktop with Chrome or Edge.
* A sensible repeater location.
* Reliable power.

<div class="sm-cx sm-cx-info">

Location matters more than almost anything else.

A modest repeater in a high, clear spot is usually more useful than a powerful setup hidden indoors.

</div>
<span id="choose-your-region-settings"></span>
=== Choose your region settings ===

Start with the baseline <code>sco</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code> and <code>eng-ne</code>, then add the local areas the repeater genuinely covers.

{| class="wikitable"
|-
! Location / coverage
! Regions to add
! Notes
|-
| Any Scottish repeater
| <code>sco</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Baseline ScotMesh setup.
|-
| Fife
| <code>sco</code>, <code>fif</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Fife-wide coverage.
|-
| Central Scotland
| <code>sco</code>, <code>cen</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Wider Central belt coverage.
|-
| Falkirk
| <code>sco</code>, <code>cen</code>, <code>fal</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Falkirk local coverage.
|-
| Edinburgh area
| <code>sco</code>, <code>cen</code>, <code>edi</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Edinburgh-facing Central Scotland coverage.
|-
| Glasgow area
| <code>sco</code>, <code>cen</code>, <code>gla</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Glasgow-facing Central Scotland coverage.
|-
| Tayside
| <code>sco</code>, <code>tay</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Wider Tayside coverage.
|-
| Dundee area
| <code>sco</code>, <code>tay</code>, <code>dun</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Dundee local coverage.
|-
| Perth area
| <code>sco</code>, <code>tay</code>, <code>per</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>
| Perth local coverage.
|-
| High site / bridge
| <code>sco</code>, <code>sco-admin</code>, <code>ioi</code>, <code>wls</code>, <code>eng-ne</code>, plus genuinely served areas
| Do not add every region just because it is listed.
|}

<span id="simple-setup-flow"></span>
=== Simple setup flow ===

# Open the MeshCore web flasher in Chrome or Edge.
# Select your device.
# Choose the repeater role.
# Use the UK / EU Narrow preset.
# Flash the device with the latest stable firmware
# Set a clear repeater name.
# Add the right regions from the table above.
# Set flood adverts to 24 hours.
# Deny wildcard forwarding.
# Set <code>region default sco</code>.
# Save the region configuration.

<span id="simple-command-examples"></span>
=== Simple command examples ===

<span id="baseline-scottish-repeater"></span>
==== Baseline Scottish repeater ====

Use this when the repeater is part of ScotMesh but does not have a more specific local region yet.

<syntaxhighlight lang="text">region def sco|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

Without <code>region default sco</code>, your repeater’s adverts are sent unscoped. The Scottish network denies unscoped forwarding (<code>region denyf *</code>), so other repeaters will reject those adverts and will not know your repeater is there.

</div>
<span id="fife-repeater"></span>
==== Fife repeater ====

Use this when the repeater serves Fife.

<syntaxhighlight lang="text">region def sco fif|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<span id="central-scotland-falkirk-repeater"></span>
==== Central Scotland / Falkirk repeater ====

Use this when the repeater serves Falkirk and wider Central Scotland.

<syntaxhighlight lang="text">region def sco cen fal|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<span id="good-repeater-habits"></span>
=== Good repeater habits ===

* Put the repeater as high and clear as you reasonably can.
* Use stable power.
* Keep the antenna vertical.
* Give the repeater a name people can recognise.
* Add only the regions it genuinely serves.
* Use <code>region denyf *</code>; do not allow wildcard forwarding.
* Set <code>region default sco</code> so your adverts are accepted by the rest of the mesh.
* Set flood adverts to 24 hours.
* Ask the community before inventing new region codes.

<span id="where-to-go-next"></span>
=== Where to go next ===

* [[MeshCore/Regions|Regions]] has the fuller region guide and more command examples.
* [[MeshCore/Scopes|Scopes]] explains what Companion App users need to set.
* [[MeshCore/Channels|Channels]] lists the agreed and proposed channels.
* [https://docs.meshcore.io/cli_commands/ MeshCore CLI Commands] is the upstream command reference.

<span id="appendix-what-the-key-commands-mean"></span>
=== Appendix: what the key commands mean ===

{| class="wikitable"
|-
! Command
! Meaning
|-
| <code>region def sco …</code>
| Define the whole region tree in one line: the default scope first, then each code, with <code>name|*</code> resetting to the root.
|-
| <code>set multi.acks 1</code>
| Turn on double ACKs.
|-
| <code>set path.hash.mode 2</code>
| Use the 3-byte path hash (avoids collisions).
|-
| <code>region denyf *</code>
| Deny unscoped wildcard forwarding.
|-
| <code>set flood.advert.interval 24</code>
| Set flood adverts to 24 hours.
|-
| <code>region default sco</code>
| Set the default scope so adverts from this repeater are scoped to <code>sco</code> and accepted by the mesh.
|-
| <code>region save</code>
| Save the region configuration.
|}

MeshCore/Regions

2026-11-03T17:21:48Z

Admin: Improve rendering + apply freshness fixes (regions/scopes/CLI to current)

{{DISPLAYTITLE:Regions}}
<span id="meshcore-regions"></span>
== MeshCore Regions ==

-----

<div class="sm-cx sm-cx-info">

'''NOTE - A Regional Framework was impelemented in the ScotMesh Meshcore Mesh at the beginning of April 2026. This was out of sheer necessity as our mesh was dying under the flood traffic from England (24,000 flood packets & 600+ messages daily). This saved our mesh from descending into a chaotic, unusable mess of incoherent rambles and frustrated messaging failures. This is why an understaning of regions is imperative to understanding where we are today.'''

</div>

-----

This guide is for '''repeater owners'''.

The aim is simple: keep the scheme readable, predictable, and usable as the network grows.

<span id="why-regions-are-needed"></span>
=== Why regions are needed ===

MeshCore messages travel through repeaters for onward routing. Whilst this is the core function, if every repeater carries every message everywhere, the network becomes noisy, inefficient and flooded with uneccessary traffic.

Regions help us:

# '''Keep local traffic local''' — In the future, a message that only matters in one area wont always need to be repeated across every part of Scotland.
# '''Reduce unnecessary radio traffic''' — LoRa is subject to a finite airtime cycle per hour (compared with Wi-Fi or mobile data), so every avoidable repeat uses valuable airtime.
# '''Improve reliability''' — Less unnecessary repeating leaves more room for useful messages.
# '''Make planning clearer''' — Regions make repeater deployment easier to map, identify needs, plan future expansion and ease of ongoing mesh maintenance.
# '''Support controlled peering''' — Strategic repeaters can deliberately carry neighbouring traffic, such as the '''IOI peering agreement''' between Scotland and the Island of Ireland.

<span id="regions-and-scopes"></span>
=== Regions and scopes ===

There are two related concepts: '''regions''' and '''scopes'''.

{| class="wikitable"
|-
! Term
! Meaning
! Example
|-
| '''Region'''
| A label configured on a repeater to describe the area it serves.
| An Edinburgh-area repeater includes <code>edi</code>.
|-
| '''Scope'''
| A label applied to messages or channels to describe which area (or region) the traffic is intended to travel.
| The <code>#glasgow</code> channel might use <code>gla</code> when traffic should stay in that area.
|}

In a densely populated mesh, a repeater should only carry scoped traffic for regions it genuinely serves. In new or embryonic meshes, this requirment will be a future need but best practise planning mandates introducing regions as early as is practical.

<span id="wildcard-forwarding-is-not-allowed-see-info-box-at-top-of-this-document-for-context."></span>
=== Wildcard forwarding is not allowed (see info box at top of this document for context). ===

The wildcard marker is:

<syntaxhighlight lang="text">*</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

The important rule is: <code>*</code> will appear as a root parent in the region tree, but wildcard forwarding must be denied.

In other words, <code>region put sco *</code> is correct, but must be preceeded by <code>region denyf *</code> .

</div>
The Scottish MeshCore setup does not allow wildcard forwarding. Repeater owners must deny wildcard forwarding with:

<syntaxhighlight lang="text">region denyf *</syntaxhighlight>
You may still see <code>*</code> as the root parent when defining the region tree, for example <code>region put sco *</code>. That is different from allowing wildcard forwarding.

For channel names and suggested scopes, see [[MeshCore/Channels|Channels]].

<span id="scottish-region-code-approach"></span>
=== Scottish region code approach ===

For Scotland, we use simple three-letter lowercase codes.

We are not part of any UK wide mesh (for context see comment box at the top of this documnet) Therefore, '''we are not using any long prefixed names'''

We use short codes such as:

<syntaxhighlight lang="text">sco
cen
fal</syntaxhighlight>
Other countries and communities may use ISO-style hierarchical codes. That is valid for them, but the Scottish convention is designed to be short and easy to read in apps, analyser tools, and community discussions.

<span id="current-june-2026-agreed-region-codes"></span>
=== Agreed region codes ===

{| class="wikitable"
|-
! Code
! Area
|-
| <code>sco</code>
| Scotland — the default scope, carried by every Scottish repeater
|-
| <code>sco-admin</code>
| Scotland-only, for bots and utilities. Never peered out.
|-
| <code>cen</code>
| Central Scotland
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>gla</code>
| Glasgow area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>sti</code>
| Stirling area (proposed)
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>dun</code>
| Dundee area
|-
| <code>per</code>
| Perth area
|-
| <code>ioi</code>
| Island of Ireland — peering root beside <code>sco</code>
|-
| <code>wls</code>
| Wales — peering root beside <code>sco</code>
|-
| <code>eng-ne</code>
| North East England — peering root beside <code>sco</code>
|}

<span id="ioi-peering-agreement"></span>
=== IOI peering agreement ===

The Scottish and Irish MeshCore communities maintain a '''peering agreement''': scoped traffic is carried on the other network only where '''both''' sides configure for it.

Under that agreement, Scottish repeaters add the <code>ioi</code> region alongside <code>sco</code> where the Scottish baseline applies, and Island of Ireland repeaters add <code>sco</code> alongside their own region codes in the same spirit. Messages with matching '''scopes''' can then move between the two networks predictably, without relying on wildcard forwarding. For example channel names and typical scopes, see [[MeshCore/Channels|Channels]].

The <code>ioi</code> code is '''not''' a Scottish local region. It marks repeaters and traffic that deliberately participate in that peering.

Do not use:

<syntaxhighlight lang="text">ioi-sco</syntaxhighlight>
Use:

<syntaxhighlight lang="text">ioi</syntaxhighlight>
<span id="peering-with-scotland-other-regions"></span>
==== Peering with Scotland (other regions) ====

If another region wants to peer with Scotland in a similar way, they should already have the following in place:

# '''Wildcard flooding disallowed''' on their repeaters (the same principle as the Scottish setup: deny wildcard forwarding with <code>region denyf *</code>; see [[#wildcard-forwarding-is-not-allowed|Wildcard forwarding is not allowed]]).
# '''Appropriate regions on their repeaters''' so traffic is not forwarded wider than intended, and Scottish repeaters are not flooded with scoped traffic they did not agree to carry.
# '''Neighbouring Scotland in RF terms''' so equipment can '''directly''' peer, rather than assuming long unofficial relay chains.

When that fits your situation, contact the Scottish Mesh community on [https://discord.gg/ytxfyuDmSt Discord] so we can discuss scope names, boundaries, and a safe rollout.

<span id="recommended-hierarchy"></span>
=== Recommended hierarchy ===

Although the hierarchy is not written into the code itself, it can be thought of like this:

<syntaxhighlight lang="text">sco
cen
edi
gla
fal
sti (proposed)
fif
tay
dun
per
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
In plain English:

* <code>sco</code> is for Scotland-wide traffic, and <code>sco-admin</code> is a Scotland-only root for bots and utilities.
* <code>cen</code>, <code>tay</code>, and <code>fif</code> are Scottish sub regions.
* <code>edi</code>, <code>gla</code>, <code>fal</code>, <code>sti</code>, <code>dun</code> and <code>per</code> are local areas.
* <code>ioi</code> (Island of Ireland), <code>wls</code> (Wales) and <code>eng-ne</code> (North East England) are peering roots beside <code>sco</code>.

<span id="suggested-repeater-configuration-policy"></span>
=== Suggested repeater configuration policy ===

A Scottish repeater should normally be configured with:

# The country code <code>sco</code>, and <code>sco-admin</code> for Scotland-only utility traffic.
# The peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code>.
# The relevant regional code.
# The relevant local code, if appropriate.
# Any neighbouring codes that the repeater genuinely serves.

<div class="sm-cx sm-cx-warning">

Do not allow wildcard forwarding.

In command line interface (CLI) examples, this means using <code>region denyf *</code>

</div>
<span id="falkirk-central-scotland-repeater"></span>
==== Falkirk / Central Scotland repeater ====

A repeater covering the Falkirk area would usually have:

<syntaxhighlight lang="text">sco
cen
fal
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
<span id="edinburgh-facing-central-scotland-repeater"></span>
==== Edinburgh-facing Central Scotland repeater ====

A repeater that mainly serves Central Scotland but has strong coverage towards Edinburgh might use:

<syntaxhighlight lang="text">sco
cen
edi
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
<span id="fife-repeater"></span>
==== Fife repeater ====

A Fife repeater would usually have:

<syntaxhighlight lang="text">sco
fif
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
If it genuinely provides useful Central Scotland coverage, it may also include:

<syntaxhighlight lang="text">cen</syntaxhighlight>
<span id="scottish-repeaters-and-ioi"></span>
==== Scottish repeaters and <code>ioi</code> ====

Scottish repeaters carry the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> alongside <code>sco</code> and <code>sco-admin</code> — these are included in every repeater script:

<syntaxhighlight lang="text">sco
sco-admin
ioi
wls
eng-ne</syntaxhighlight>
That keeps peering-capable forwarding available where the Scottish baseline is configured. It does not make <code>ioi</code> a Scottish local region.

<span id="good-practice-for-repeater-owners"></span>
=== Good practice for repeater owners ===

Use lowercase region codes. Do not use mixed case such as <code>SCO</code>, <code>Cen</code>, or <code>FAL</code>.

Use agreed codes. For example, use <code>edi</code> for the Edinburgh area, not <code>edn</code>, <code>edinburgh</code>, or <code>gb-edi</code>.

Add only the areas your repeater genuinely serves. A high-site repeater may reasonably serve several areas, but a repeater should not claim every region just because it can occasionally hear distant nodes.

Coordinate before adding new codes. If a new area needs a code, discuss it publicly before using it so that the community does not end up with competing names for the same place.

<span id="suggested-command-examples"></span>
=== Suggested command examples ===

The exact method may vary depending on firmware version and whether you are using the app, web configurator, USB serial, or remote administration. The upstream reference is the MeshCore [https://docs.meshcore.io/cli_commands/ CLI Commands] documentation, especially the region management commands.

<div class="sm-cx sm-cx-info">

New to repeater setup?

Start with [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]], then come back here for the fuller detail.

</div>
On current firmware (1.16+) the whole region tree goes in one <code>region def</code> line, followed by <code>region denyf *</code> and the standard <code>set</code> commands. The easiest way to get the exact script for your area is the [https://meshcore.scotmesh.net/repeater/ ScotMesh repeater builder]; the examples below show what it produces.

For a Central Scotland / Falkirk repeater:

<syntaxhighlight lang="text">region def sco cen fal|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
Then check the result with:

<syntaxhighlight lang="text">region</syntaxhighlight>
For a Tayside / Dundee repeater:

<syntaxhighlight lang="text">region def sco tay dun|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
For a Glasgow-area repeater:

<syntaxhighlight lang="text">region def sco cen gla|* sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
For a repeater that serves Scotland, Central Scotland, Glasgow, Edinburgh, and IOI peering (<code>ioi</code>):

<syntaxhighlight lang="text">region def sco cen|* gla|cen edi|cen sco-admin|* ioi|* wls|* eng-ne
region denyf *
set flood.advert.interval 24
set multi.acks 1
set path.hash.mode 2
region default sco
region save</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

'''Set <code>region default sco</code> on your repeater.'''

Without a default scope, adverts sent by your repeater go out unscoped. Because the Scottish network uses <code>region denyf *</code>, other repeaters will reject those unscoped adverts and will never learn your repeater exists. Setting the default scope to <code>sco</code> ensures your adverts are carried normally across the mesh.

</div>
This is separate from flood forwarding permissions. For more detail, see [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

Always check for an <code>OK</code> response where applicable, and remember to save the configuration so it survives a reboot.

<span id="firmware-and-app-version-notes"></span>
=== Firmware and app version notes ===

Region and scope support depends on MeshCore firmware and app support.

Use the latest stable MeshCore firmware and app available for your device. Older firmware may still pass some traffic, but region management and scope handling may not behave as expected.

MeshCore region filtering was introduced across firmware and app releases, and default scope support was added later. The MeshCore posts [https://blog.meshcore.io/2026/01/20/region-filtering Region Filtering] and [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region] are useful background when checking version behaviour.

<span id="naming-and-publishing-new-region-codes"></span>
=== Naming and publishing new region codes ===

When a new Scottish area needs a code, use these rules:

# Use three lowercase letters.
# Make the code obvious to local users.
# Avoid clashing with existing agreed codes.
# Avoid overly small areas unless there is a real need.
# Discuss the code with the local MeshCore community before publishing it.

Examples of possible future codes might include:

<syntaxhighlight lang="text">sti = Stirling
liv = Livingston
abe = Aberdeen
inv = Inverness
ayr = Ayrshire
bor = Borders</syntaxhighlight>
These are examples only and should not be treated as agreed until the community confirms them.

<span id="common-questions"></span>
=== Common questions ===

<span id="do-regions-replace-normal-meshcore-messaging"></span>
==== Do regions replace normal MeshCore messaging? ====

No. Regions help control where scoped traffic is repeated.

<span id="should-every-scottish-repeater-have-sco-and-ioi"></span>
==== Should every Scottish repeater have the same baseline? ====

Yes. Every Scottish repeater carries <code>sco</code>, plus <code>sco-admin</code> and the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> — these are included in every repeater script.

<span id="should-every-repeater-have-every-scottish-region"></span>
==== Should every repeater have every Scottish region? ====

No. That would defeat the purpose of regions. Repeaters should only list the areas they genuinely serve.

<span id="should-we-use-gb-sco-instead-of-sco"></span>
==== Should we use <code>gb-sco</code> instead of <code>sco</code>? ====

Not for this Scottish scheme. Some wider UK or international guides use ISO-style codes, but the local Scottish agreement is to use short three-letter codes.

<span id="can-a-repeater-be-in-more-than-one-region"></span>
==== Can a repeater be in more than one region? ====

Yes. That is useful for high sites, border areas, or repeaters that genuinely link neighbouring areas.

<span id="can-we-allow-for-compatibility"></span>
==== Can we allow <code>*</code> for compatibility? ====

No. The Scottish MeshCore setup does not allow wildcard forwarding. Use the correct region scope instead.

<span id="summary"></span>
=== Summary ===

Regions give the Scottish MeshCore community a simple way to organise the network as it grows.

Our agreed approach is:

* Use three-letter lowercase codes.
* Use <code>sco</code> for Scotland.
* Carry <code>sco-admin</code> and the peering roots <code>ioi</code>, <code>wls</code> and <code>eng-ne</code> alongside <code>sco</code> on every repeater.
* Use <code>cen</code>, <code>tay</code>, <code>gla</code>, and <code>fif</code> for major regions where they match coverage.
* Use <code>fal</code>, <code>edi</code>, <code>gla</code>, <code>dun</code>, and <code>per</code> for local areas.
* Use <code>ioi</code> for Island of Ireland traffic under the IOI peering agreement.
* Deny wildcard forwarding with <code>region denyf *</code>.
* Do not use long prefixes such as <code>gb-sco</code> or <code>sco-fal</code> in this local scheme.

This gives us a clean, readable, and expandable foundation for building a coordinated Scottish MeshCore network.

MeshCore/Scopes

2026-11-03T17:21:44Z

Admin: Improve rendering + apply freshness fixes (regions/scopes/CLI to current)

{{DISPLAYTITLE:Scopes}}
<span id="meshcore-scopes"></span>
== MeshCore Scopes ==

<div class="sm-cx sm-cx-success">

'''Quick start for most users:''' open the app, go to '''Experimental Settings''', set '''Default Scope Region''' to <code>sco</code>. That is all you need for normal Scottish traffic.

</div>
<div class="sm-cx sm-cx-warning">

'''Watch out:''' if you do not have a suitable '''scope''' set, repeaters on the Scottish MeshCore network wont forward your traffic. You can end up '''shouting into the void'''. Check your default scope and each channel’s scope before you count on messages reaching anyone.

</div>
Scope is the single setting that makes or breaks whether your messages go anywhere on ScotMesh. The channel name is for people — the scope is for the mesh. Set your '''default''' to <code>sco</code>, then adjust per channel when you need something narrower.

<div class="sm-cx sm-cx-info">

'''ScotMesh setup:''' Under '''Experimental Settings''', set the default scope region to <code>sco</code>, and keep <code>ioi</code> available in your scope list as well so you can pick it when you need it. For each channel, set scope to match '''where the traffic should travel'''—for example <code>#edinburgh</code> with <code>edi</code>. On '''<code>#ireland</code>''', you may use '''<code>ioi</code> or <code>sco</code>''': use <code>ioi</code> when the message should ride the Island of Ireland scoped path (IOI peering); use <code>sco</code> when you want the same channel but Scotland-wide scoped carriage on the mesh.

</div>
<span id="why-scope-matters"></span>
=== 🤷 Why scope matters ===

Without scope, repeaters have no way to know whether to carry your traffic. With it, messages travel through exactly the right part of the network.

* Keep Scottish traffic inside Scotland where appropriate.
* Allow controlled traffic to and from the Island of Ireland (IOI peering).
* Reduce unnecessary flooding.
* Keep the network easier to grow.

For example channel names and typical scopes, see [[MeshCore/Channels|Channels]]. For repeater region codes, see [[MeshCore/Regions|Regions]].

<span id="what-region-scope-means"></span>
=== 🗺️ What region scope means ===

Think of scope like a postcode on a letter — it tells the mesh where the message is meant to go.

<syntaxhighlight lang="text">sco = Scotland-wide
edi = Edinburgh area (example local)
ioi = Island of Ireland (IOI peering)</syntaxhighlight>
A message scoped to <code>sco</code> is forwarded by repeaters that carry <code>sco</code>as a region. A message scoped to <code>ioi</code> is forwarded by repeaters that carry <code>ioi</code>as a region. If scope is missing or wrong for your path, the message will go nowhere, it is dropped and ceases to exist.

<span id="wildcard-forwarding-is-not-allowed"></span>
=== 🚫 Wildcard forwarding is not allowed ===

The wildcard marker is <code>*</code>. Do not rely on it for routing — the Scottish MeshCore setup expects explicit region scopes.

In the '''Companion App''', your channel scope should always be a '''real region code''' (<code>sco</code>, <code>gla</code>, <code>ioi</code>, and so on). On '''repeaters''', CLI examples sometimes show <code>*</code> as the '''parent''' in a region tree (for example <code>region put sco *</code>); that is a different idea from wildcard '''forwarding''' and is covered in [[MeshCore/Regions|Regions]].

<span id="documented-scope-codes"></span>
=== 📋 Documented scope codes ===

{| class="wikitable"
|-
! Scope
! Typical use
|-
| <code>sco</code>
| Scotland-wide traffic
|-
| <code>sco-admin</code>
| Scotland-only, for bots and utilities (never peered out)
|-
| <code>cen</code>
| Central Scotland
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>gla</code>
| Glasgow area
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>sti</code>
| Stirling area
|-
| <code>per</code>
| Perth area
|-
| <code>dun</code>
| Dundee area
|-
| <code>ioi</code>
| Island of Ireland / IOI peering
|-
| <code>wls</code>
| Wales — peering
|-
| <code>eng-ne</code>
| North East England — peering
|}

For most day-to-day traffic in Scotland, '''<code>sco</code>''' is the right default. Use a '''local''' code when traffic should stay in that area, regardless of channel name.

<span id="default-scope-and-per-channel-scope"></span>
=== ⚙️ Default scope and per-channel scope ===

On ScotMesh, set your '''default''' scope region to <code>sco</code>. In the mobile app this is usually under '''Experimental Settings'''. Flood packets from the companion then use <code>sco</code> unless a '''group channel''' has its own scope.

'''Per-channel scope overrides the default.''' Examples:

* <code>#glasgow</code> with <code>gla</code> keeps traffic in the Glasgow-area part of the mesh.
* '''<code>#ireland</code> with <code>ioi</code>''' — message is scoped for the Island of Ireland path (IOI peering repeaters).
* '''<code>#ireland</code> with <code>sco</code>''' — same channel name, but the packet is Scotland-wide scoped; repeaters treat it like other <code>sco</code> traffic.

Keep both <code>sco</code> and <code>ioi</code> in your available scopes so you can switch. For background, see MeshCore [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

<span id="how-to-set-region-scope-in-the-companion-app"></span>
=== 📱 How to set region scope in the Companion App ===

Menus vary by app version and platform; the usual flow is:

<syntaxhighlight lang="text">1. Open the MeshCore Companion App
2. Open the channel you want to use
3. Open the channel options or channel menu
4. Find the region scope option
5. Select or add the region code you need
6. Send with that scope active</syntaxhighlight>
Often the channel menu includes something like '''Set Region Scope''', then you pick or type the code (for example <code>sco</code>, <code>edi</code>, or <code>ioi</code>).

<span id="examples"></span>
=== 💬 Examples ===

'''Scotland-wide'''

<syntaxhighlight lang="text">Channel: #scotland
Scope: sco</syntaxhighlight>
'''Local (example)'''

<syntaxhighlight lang="text">Channel: #glasgow
Scope: gla</syntaxhighlight>
'''<code>#ireland</code> with Island of Ireland scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope: ioi</syntaxhighlight>
'''<code>#ireland</code> with Scotland-wide scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope: sco</syntaxhighlight>
The channel name does not set scope by itself — you still choose <code>ioi</code> or <code>sco</code> (or another code) in the channel settings.

<span id="quick-choices"></span>
=== ⚡ Quick choices ===

* Normal Scottish chat: default <code>sco</code>, or <code>#scotland</code> with <code>sco</code>.
* Local-only: local scope such as <code>edi</code> or <code>gla</code> when traffic should stay in that area.
* '''<code>#ireland</code>:''' <code>ioi</code> for IOI-scoped path, '''<code>sco</code>''' when you want Scotland-wide scoped carriage on that channel.
* Tests: <code>#test</code> with whichever scope you are testing (<code>tay</code>, <code>sco</code>, …).

If you are unsure, '''<code>sco</code>''' is the safe general default for Scottish-side traffic.

<span id="what-to-avoid"></span>
=== ❌ What to avoid ===

* Sending traffic with no region scope.
* Relying on wildcard forwarding.
* Assuming the channel name alone chooses routing.

<span id="summary"></span>
=== 📝 Summary ===

<syntaxhighlight lang="text">Default: sco on ScotMesh
Override per channel when needed
#ireland: ioi OR sco
Local: use the local code when traffic should stay local
Check your companion app is scoped before you send your initial messages</syntaxhighlight>
Getting scope right keeps mesh traffic logical and the mesh relaible, easier to use and simpler to grow.

MediaWiki:Common.css

2026-11-03T17:15:12Z

Admin: mc-pagelogo style

/* ScotMesh content styles. Core brand (colours/fonts/cards) is render-blocking in LocalSettings. */
.sm-cx{border-radius:6px;padding:.15rem 1rem;margin:1rem 0;border-left:4px solid #22324D;background:#101C30}
.sm-cx-info{border-left-color:#005EB8}
.sm-cx-warning{border-left-color:#F2B33D}
.sm-cx-success{border-left-color:#65C281}
.sm-cx > :first-child{margin-top:.65rem}
.sm-cx > :last-child{margin-bottom:.65rem}
/* front-page community join */
.sm-join{display:flex;flex-wrap:wrap;gap:.7rem;margin:1rem 0 .4rem}
.sm-join a{display:inline-flex;align-items:center;gap:.5rem;font-family:"IBM Plex Mono",ui-monospace,monospace;font-weight:600;font-size:.92rem;text-decoration:none;padding:.65rem 1.2rem;border-radius:999px;border:1px solid #22324D;transition:border-color .15s,background .15s}
.j-discord a{background:#5865F2;border-color:#5865F2;color:#fff}
.j-discord a:hover{background:#4654d0;border-color:#4654d0}
.j-forum a{background:#101C30;color:#E6EDF7}
.j-forum a:hover{border-color:#005EB8;color:#fff}
.sm-join-note{display:block;font-family:"IBM Plex Mono",ui-monospace,monospace;font-size:.82rem;color:#8FA2BD;margin:.2rem 0 0}
.sm-join-note code{color:#E6EDF7;background:#0C1729;border:1px solid #22324D;padding:.05rem .4rem;border-radius:3px}
/* network lockup at the top of a network section page */
.mc-pagelogo{display:block;margin:.2rem 0 1.3rem}
.mc-pagelogo img,.mc-pagelogo .mw-file-element{width:min(240px,62%);height:auto}

MeshCore

2026-11-03T17:15:11Z

Admin: Add scotmesh/meshcore lockup to MeshCore landing

MediaWiki:Sidebar

2026-11-03T17:06:34Z

Admin: Sidebar: full MeshCore nav

Main Page

2026-11-03T17:06:33Z

Admin: Hero: ScotMesh logo + Join the Discord

__NOTOC__ __NOEDITSECTION__
<div class="sm-hero">
<div class="sm-herologo">[[File:ScotMesh-lockup.svg|link=|alt=ScotMesh|260px]]</div>
<div class="sm-h1">Two meshes across Scotland, one wiki.</div>
<p class="sm-lead">Guides, setup and reference for both ScotMesh radio networks — MeshCore and Meshtastic. Pick a network to get started.</p>
<div class="sm-btns"><span class="b-discord">[https://discord.gg/ytxfyuDmSt Join the Discord]</span> <span>[https://scotmesh.uk Forum]</span></div>
</div>

<div class="sm-grid">
<div class="net-card meshcore">
<div class="net-head">[[File:ScotMesh-meshcore-mark.svg|link=MeshCore|38px|alt=MeshCore]]<span class="net-meta"><span class="net-name">MeshCore</span><span class="net-for">Held Up by Repeaters</span></span></div>
<p>Long-range LoRa on cheap radios, carried by fixed repeaters on high ground. Getting started, regions, scopes, channels, repeater setup and the FAQ.</p>
<div class="net-go">[[MeshCore|Open the MeshCore guides →]]</div>
</div>
<div class="net-card meshtastic">
<div class="net-head">[[File:ScotMesh-meshtastic-mark.svg|link=Meshtastic|38px|alt=Meshtastic]]<span class="net-meta"><span class="net-name">Meshtastic</span><span class="net-for">Scotland's Original Mesh</span></span></div>
<p>Long-range LoRa messaging with an app on your phone, where every radio can repeat what it hears. Introduction and setup guides.</p>
<div class="net-go">[[Meshtastic|Open the Meshtastic guides →]]</div>
</div>
</div>

<span class="sm-join-note">Forum invite code <code>VVAGXJN7BQ</code></span>

MeshCore/TX Delay and Flood Propagation

2026-11-03T17:06:31Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:TX Delay and Flood Propagation}}
<span id="tx-delay-and-flood-propagation-on-scotmesh"></span>
== TX Delay and Flood Propagation on ScotMesh ==

<blockquote>'''Key point:''' TX Delay scales a randomized waiting window before a repeater forwards flood traffic. A lower value creates a smaller window and can statistically bias that repeater toward earlier forwarding. It is not a routing table, does not prescribe a route, and does not guarantee which repeater transmits first.
</blockquote>
<span id="purpose-and-scope"></span>
=== Purpose and scope ===

This page explains how ScotMesh repeater operators can use TX Delay as a coordinated network-planning setting. It combines the current MeshCore implementation and command reference with a practical decision flow derived from Sydney Mesh guidance and published by the Island of Ireland LoRa Project.

The recommendations are useful defaults, not automatic proof that a site should receive a particular setting. RF coverage, neighbour relationships, network density, firmware behaviour and observed traffic should all be reviewed before changing a deployed repeater.

<span id="what-tx-delay-actually-does"></span>
=== What TX Delay actually does ===

For flood traffic, a MeshCore repeater estimates the packet airtime, multiplies it by the configured TX Delay factor, and chooses a random retransmission delay from a window based on that result. In the current repeater source, the effective calculation is:

<syntaxhighlight lang="text">t = estimated packet airtime x txdelay
random delay = 0 to (5 x t), inclusive in the implementation</syntaxhighlight>
The random waiting window is primarily a collision-avoidance mechanism. When several nearby repeaters hear the same flood packet, spreading their forwarding times reduces the chance that they all transmit simultaneously.

A larger factor widens the random window and can reduce collision risk, but adds potential latency. A lower factor narrows the window and makes earlier forwarding statistically more likely, but never certain.

<span id="worked-example"></span>
==== Worked example ====

For illustration, if a packet has an estimated airtime of 500 ms, the approximate random forwarding windows are:

{| class="wikitable"
|-
! style="text-align: right;"| TX Delay
! style="text-align: right;"| Approximate random forwarding window
|-
| style="text-align: right;"| 0.25
| style="text-align: right;"| 0-625 ms
|-
| style="text-align: right;"| 0.3
| style="text-align: right;"| 0-750 ms
|-
| style="text-align: right;"| 0.6
| style="text-align: right;"| 0-1,500 ms
|-
| style="text-align: right;"| 1.0
| style="text-align: right;"| 0-2,500 ms
|-
| style="text-align: right;"| 1.4
| style="text-align: right;"| 0-3,500 ms
|-
| style="text-align: right;"| 2.0
| style="text-align: right;"| 0-5,000 ms
|}

''Illustrative values calculated from the current source formula; actual airtime depends on the packet and radio parameters.''

<blockquote>'''Important limitation:''' Do not describe TX Delay as a mechanism that necessarily cancels a scheduled retransmission when another repeater is heard. The current TX Delay setting controls the random retransmission window. A separate proposal to add configurable suppression after hearing other repeats shows that this behaviour should not be attributed to TX Delay itself.
</blockquote>
<span id="timing-influence-not-route-selection"></span>
=== Timing influence, not route selection ===

MeshCore flood propagation is not conventional shortest-path routing. Multiple repeaters may receive and forward a flood packet, and the observed path is shaped by RF reception, topology, packet timing, hop limits and the behaviour of participating nodes.

Because lower-delay repeaters draw from a smaller random window, a coordinated hierarchy can bias strategically useful infrastructure toward earlier forwarding opportunities. This is a probability effect across repeated events, not a priority flag.

It does not guarantee that a hilltop repeater wins any particular forwarding race, that another repeater will remain silent, or that a packet follows the geographically shortest path.

<span id="the-sydney-derived-tx-delay-decision-flow"></span>
=== The Sydney-derived TX Delay decision flow ===

The Island of Ireland LoRa Project publishes a sequential decision flow based on Sydney Mesh advice and adapted for its own network. For ScotMesh, the same flow is best treated as a starting framework: ask the questions in order and stop at the first '''Yes''' answer.

<blockquote>'''Why order matters:''' A newly installed mountaintop repeater still matches “Just placed - under 3 days?” before it reaches the mountaintop question. The conservative <code>1.4</code> setting therefore comes first while its real RF role is observed.
</blockquote>
{| class="wikitable"
|-
! style="text-align: right;"| Step
! Question - stop at the first '''Yes'''
! style="text-align: right;"| Suggested <code>txdelay</code>
|-
| style="text-align: right;"| 1
| First repeater setup?
| style="text-align: right;"| '''1.4'''
|-
| style="text-align: right;"| 2
| Temporary or short-term placement?
| style="text-align: right;"| '''1.4'''
|-
| style="text-align: right;"| 3
| Just placed - under 3 days?
| style="text-align: right;"| '''1.4'''
|-
| style="text-align: right;"| 4
| Few neighbours - 3 or fewer?
| style="text-align: right;"| '''1.4'''
|-
| style="text-align: right;"| 5
| Attic, window or below roofline?
| style="text-align: right;"| '''1.0'''
|-
| style="text-align: right;"| 6
| Primarily connects its owner to the mesh?
| style="text-align: right;"| '''1.0'''
|-
| style="text-align: right;"| 7
| Above-roofline mast or top of apartment block?
| style="text-align: right;"| '''0.6'''
|-
| style="text-align: right;"| 8
| Hill overlooking a neighbourhood?
| style="text-align: right;"| '''0.6'''
|-
| style="text-align: right;"| 9
| Mountaintop with views for miles?
| style="text-align: right;"| '''0.3'''
|-
| style="text-align: right;"| 10
| Directional antenna or specialist link?
| style="text-align: right;"| '''0.25'''
|-
| style="text-align: right;"| 11
| Mobile or vehicle repeater?
| style="text-align: right;"| '''2.0'''
|-
| style="text-align: right;"| Else
| None of the above
| style="text-align: right;"| '''1.4'''
|}

''These values reproduce the published decision flow. They are community planning guidance, not MeshCore firmware defaults and not a guarantee of path behaviour.''

<span id="how-to-interpret-the-values"></span>
==== How to interpret the values ====

* '''2.0 - mobile or vehicle:''' a deliberately broad window for a changing, non-fixed RF role.
* '''1.4 - new, temporary, lightly connected or unclassified:''' the conservative starting point used by the published flow.
* '''1.0 - domestic or local-access site:''' typically below roofline or mainly connecting one operator.
* '''0.6 - useful elevated local infrastructure:''' above-roofline mast, apartment-block roof or neighbourhood hill.
* '''0.3 - major wide-area mountaintop infrastructure:''' after the site’s role has been demonstrated.
* '''0.25 - directional or specialist link:''' reviewed as part of the wider topology.

A lower number is not an upgrade. It represents a narrower timing window and should be justified by the repeater’s stable, observed role.

<span id="geographically-surprising-paths"></span>
=== Geographically surprising paths ===

Observed flood paths can appear indirect on a map even when every individual RF hop is valid. The image below is a real ScotMesh example in western Scotland.

<div class="figure">

[[File:Scotmesh-tx-delay-route.jpg|thumb|right|400px|TX delay worked example route]]

</div>
''Figure 1. Example of an observed ScotMesh path in western Scotland: MUIRSHIEL-TT1 -> ARDROSSAN-RPT -> AYR-RPT -> GALLOWAY-TT1. The path is geographically indirect, but the image alone does not show that any RF link or repeater is faulty.''

This example demonstrates why a flood path should not be interpreted as a conventional shortest route. Coordinated TX Delay values may influence the relative timing of repeaters participating in the flood and may make some forwarding patterns more or less likely over time. They do not prescribe this path, prevent it, or guarantee a different one.

<blockquote>'''Read the evidence carefully:''' Use path traces as a prompt for investigation, not as proof that one TX Delay value caused the route. Compare repeated observations, neighbour data, RF coverage and traffic conditions before changing settings.
</blockquote>
<span id="practical-guidance-for-scotmesh"></span>
=== Practical guidance for ScotMesh ===

<span id="for-a-new-or-newly-moved-repeater"></span>
==== For a new or newly moved repeater ====

* Start at <code>1.4</code> and leave the repeater in its intended permanent position.
* Keep it at <code>1.4</code> for at least the first three days, consistent with the published decision flow.
* Record its neighbours, reliable coverage and repeated path observations; avoid judging it from a single trace.
* Classify the site by what it demonstrably contributes to the network, not only by height or predicted coverage.
* Coordinate any reduction with nearby ScotMesh operators, particularly where coverage overlaps.

<span id="for-an-established-repeater"></span>
==== For an established repeater ====

* Review whether the current value matches the site’s actual role and stability.
* Change one variable at a time, note the date and reason, then compare behaviour over a meaningful observation period.
* Do not lower values simply to make a node “win”. Too many narrow windows can increase simultaneous competition and undermine collision avoidance.
* If a path is surprising, check RF reachability, neighbour counts, firmware versions, scope and hop settings alongside TX Delay.

<span id="cli-examples"></span>
=== CLI examples ===

Read the current flood TX Delay value:

<syntaxhighlight lang="text">get txdelay</syntaxhighlight>
Set the conservative starting value:

<syntaxhighlight lang="text">set txdelay 1.4</syntaxhighlight>
Example for an established elevated local site after review:

<syntaxhighlight lang="text">set txdelay 0.6
get txdelay</syntaxhighlight>
The current MeshCore CLI documents TX Delay as a factor from <code>0</code> to <code>2</code>. The commands above concern flood traffic. Direct, non-flood routed traffic uses the separate <code>direct.txdelay</code> setting; do not change it merely to mirror this guide.

<span id="review-checklist"></span>
=== Review checklist ===

* Is the repeater permanently installed and observed for at least three days?
* Does it have more than three useful neighbours?
* Is the proposed classification supported by real RF coverage?
* Have repeated traces been reviewed rather than a single path?
* Have neighbouring operators considered the change as a coordinated system?
* Is the change recorded so its effect can be compared later?

<span id="summary"></span>
=== Summary ===

<blockquote>'''In one line:''' TX Delay -> randomized flood retransmission window -> statistical timing bias -> possible influence on flood propagation; never a guaranteed route.
</blockquote>
Start conservatively, observe the site, and coordinate lower settings where the repeater’s stable network role justifies a narrower random window. Treat unexpected routes as evidence to investigate, not behaviour that TX Delay alone can promise to fix.

<span id="credits-and-sources"></span>
=== Credits and sources ===

The decision flow and community guidance are based on the [https://loraproject.ie/repeater/#tx-delay Island of Ireland LoRa Project’s Repeater Setup and TX Delay guide]. That page credits Sydney Mesh advice as the basis for its recommendations, adapted for Ireland.

* [https://github.com/meshcore-dev/MeshCore/blob/main/docs/cli_commands.md#view-or-change-the-retransmit-delay-factor-for-flood-traffic MeshCore CLI commands - TX Delay]
* [https://github.com/meshcore-dev/MeshCore/blob/main/examples/simple_repeater/MyMesh.cpp MeshCore simple repeater source - <code>MyMesh.cpp</code>]
* [https://github.com/meshcore-dev/MeshCore/issues/2442 MeshCore issue #2442 - proposal for repeat suppression]

''Source and firmware behaviour checked 30 August 2026. Review this page when MeshCore forwarding behaviour or CLI semantics change.''
content here

MeshCore/MeshMapper-Friendly Repeaters

2026-11-03T17:06:29Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:MeshMapper-Friendly Repeaters}}
<span id="meshmapper-friendly-repeater-configuration-spec-for-scotmesh-meshcore"></span>
== MeshMapper-Friendly Repeater Configuration Spec for Scotmesh MeshCore ==

These are guidelines for a uniform configuration of repeaters taking part in '''Scotmesh MeshCore'''.

These are not hard and fast rules, but certain specifications are necessary for smooth MeshMapper reporting. Using these settings will help ensure a smooth-running mesh.

-----

<span id="identification"></span>
=== Identification ===

Use '''ASCII characters only''' for the repeater name.

This makes MeshMapper management much easier, as most emoji characters are '''not''' read by MeshMapper.

You can use a single emoji to customise your MeshCore app icon on your companion radio, but this has no effect on the repeater name as seen by MeshMapper.

-----

<span id="location"></span>
=== Location ===

Repeater location should be set as accurately as possible, while still protecting the safety and security of the repeater site.

For example, setting the repeater location around '''200 metres''' from the real location gives a search area of approximately '''12.6 hectares'''. This would take a careful walking search of around '''8 hours''' to cover.

Setting the location '''200–250 metres away''' from the real position gives a useful level of obfuscation while still allowing the repeater to appear correctly on MeshMapper.

If no location is set:

* The repeater will be excluded from MeshMapper
* You will not see useful telemetry, such as zero-hop neighbours
* Routing path analysis, enhancements and other mesh planning will not be possible

-----

<span id="basic-owner-information"></span>
=== Basic Owner Information ===

Please ensure basic owner information is set.

-----

<span id="advert-settings"></span>
=== Advert Settings ===

Recommended settings:

* '''Zero-hop advert:''' 60–120 minutes
* '''Flood advert:''' 24 hours

-----

<span id="radio-settings"></span>
=== Radio Settings ===

Please use:

* '''EU/UK Narrow'''
* '''Frequency:''' 869.618 MHz
* '''Spreading Factor:''' SF8
* '''Coding Rate:''' CR8
* '''Bandwidth:''' 62.5 kHz

Recommended CLI settings:

<syntaxhighlight lang="text">set multi.acks 1
set path.hash.mode 2</syntaxhighlight>
This enables:

* '''Multi ACKs'''
* '''3-byte path hash'''

Please keep your repeater updated with the latest firmware whenever possible.

Please also ensure your companion radio or radios are set to:

* '''Double ACKs on'''
* '''3-byte path hash'''

-----

<span id="access"></span>
=== Access ===

Do not leave the guest login with no password.

For continuity, please set the guest password to:

<syntaxhighlight lang="text">hello</syntaxhighlight>
This gives at least some security over the guest login.

Keep your admin password safe.

-----

<span id="region-scope"></span>
=== Region / Scope ===

Please set both the '''default scope''' and '''home scope''' to:

<syntaxhighlight lang="text">sco</syntaxhighlight>
Please also deny flood to:

<syntaxhighlight lang="text">*</syntaxhighlight>
Channels set to region <code>sco</code> are:

* <code>Public</code>
* <code>#scotland</code>

Optionally, you may also add the channel:

<syntaxhighlight lang="text">#ireland</syntaxhighlight>
with region:

<syntaxhighlight lang="text">ioi</syntaxhighlight>
Scotland and the Island of Ireland have collaborated very well to construct a civilised MeshCore environment.

As Scotmesh expands, we may add nested sub-regions within <code>sco</code>.

-----

<span id="time-setting-and-synchronisation-with-meshmapper"></span>
=== Time Setting and Synchronisation with MeshMapper ===

After power-up of the repeater, the time is always incorrect.

Please use the following procedure to set the correct time and synchronise it with MeshMapper.

This process assumes you have already configured the repeater for use.

<span id="phone-app-method"></span>
==== Phone App Method ====

# Open the settings page in the phone app.
# Perform the usual '''Sync Clock''' action.
# Scroll to the bottom of the page.
# Tap '''Reboot'''.

Unlike pressing the physical '''reset''' button on the repeater board, this is a '''soft reset'''.

A soft reset does '''not''' reset the clock, but it appears to be important for finalising certain settings.

For reference:

* Pressing '''Reboot''' in the app is a '''soft reset'''
* Pressing the physical reset button on the board is a '''hard reset'''
* A hard reset resets all settings not stored in flash

You may also use CLI commands to perform the same task if preferred.

-----

<span id="closing-note"></span>
=== Closing Note ===

I hope this helps with the ease of configuration.

This guide assumes you already understand the menu and command structure of MeshCore repeaters, devices and apps.

If there is a menu item you cannot find, ask on the Discord server and one of the admins or knowledgeable users will help you along.ur content here

MeshCore/OTA Upgrade Process

2026-11-03T17:06:28Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:OTA Upgrade Process}}
<span id="upgrading-meshcore-repeaters-using-ota"></span>
== Upgrading MeshCore Repeaters Using OTA ==

This guide explains how to upgrade a MeshCore repeater or room server using the OTA function.

OTA means '''Over The Air'''. It allows firmware to be upgraded without physically connecting the repeater to a computer by USB. This is useful for repeaters already installed on roofs, masts, poles, lofts or other awkward locations.

<blockquote>'''Important:''' OTA is convenient, but it still carries some risk. Make sure you use the correct firmware for the correct hardware.
</blockquote>

-----

<span id="supported-ota-methods"></span>
=== Supported OTA methods ===

There are two common OTA methods depending on the hardware type:

{| class="wikitable"
|-
! Hardware type
! Common examples
! OTA method
|-
| nRF52 devices
| RAK4631, Heltec T114, Seeed XIAO nRF52840, SenseCAP nRF devices
| Bluetooth DFU using the '''nRF Device Firmware Update''' app
|-
| ESP32 devices
| Heltec V3, some ESP32 repeaters/room servers
| Temporary Wi-Fi access point called '''MeshCore OTA'''
|}

If you are not sure which method applies, check the device hardware before starting.

-----

<span id="before-you-start"></span>
=== Before you start ===

Before upgrading, make sure you have:

* Admin access to the repeater or room server.
* A recent copy or screenshot of the repeater settings.
* The correct firmware for the exact hardware model.
* A phone or tablet with Bluetooth enabled for nRF devices.
* Good battery level on your phone.
* The repeater has enough power to complete the update.
* You are physically close enough for a reliable Bluetooth or Wi-Fi connection.

For solar repeaters, avoid doing OTA updates when the battery is low or the weather is poor.

-----

<span id="firmware-file-warning"></span>
=== Firmware file warning ===

When downloading firmware, make sure you select the correct file.

<span id="for-nrf52-ota-updates"></span>
==== For nRF52 OTA updates ====

Use the firmware '''ZIP''' file intended for DFU / OTA update.

Do '''not''' unzip it unless the instructions for your specific device say otherwise.

<span id="for-esp32-ota-updates"></span>
==== For ESP32 OTA updates ====

Use the firmware file that does '''not''' contain <code>merged</code> in the filename.

<blockquote>'''Do not use a merged firmware file for OTA.'''

A merged firmware file is normally for a full USB flash and may wipe or reset the device.
</blockquote>

-----

<span id="download-the-firmware"></span>
=== Download the firmware ===

<ol style="list-style-type: decimal;">
<li><p>Go to the MeshCore flasher:</p>
<p>https://flasher.meshcore.io</p></li>
<li><p>Select the correct device type.</p></li>
<li><p>Select the correct role, usually:</p>
<ul>
<li><code>Repeater</code></li>
<li><code>Room Server</code></li>
<li><code>Room Server / Repeater</code></li></ul>
</li>
<li><p>Download the correct firmware file for your hardware.</p></li>
<li><p>Save the file somewhere easy to find on your phone or computer.</p></li></ol>

-----

<span id="method-1-ota-update-for-nrf52-devices"></span>
== Method 1: OTA update for nRF52 devices ==

Use this method for devices such as:

* RAK4631
* Heltec T114
* Seeed XIAO nRF52840
* SenseCAP nRF-based devices

-----

<span id="step-1-install-the-dfu-app"></span>
=== Step 1 — Install the DFU app ===

Install the Nordic '''nRF Device Firmware Update''' app.

* iOS: search the App Store for <code>nRF Device Firmware Update</code>
* Android: search Google Play for <code>nRF Device Firmware Update</code>

-----

<span id="step-2-connect-to-the-repeater-in-meshcore"></span>
=== Step 2 — Connect to the repeater in MeshCore ===

# Open the MeshCore app.
# Connect to the repeater or room server.
# Log in using the admin password.
# Open the repeater management screen.
# Open the command line / terminal.

-----

<span id="step-3-put-the-repeater-into-ota-mode"></span>
=== Step 3 — Put the repeater into OTA mode ===

In the MeshCore command line, enter:

<syntaxhighlight lang="text">start ota</syntaxhighlight>
The device should reply:

<syntaxhighlight lang="text">OK</syntaxhighlight>
The repeater is now in OTA / DFU mode.

Leave the repeater powered on and do not restart it while you move to the DFU app.

<span id="step-4-configure-the-dfu-app"></span>
=== Step 4 — Configure the DFU app ===

Open the '''nRF Device Firmware Update''' app.

Recommended settings:

* Enable '''Packets receipt notifications'''
* Set the number of packets to:

{| class="wikitable"
|-
! Device
! Packet setting
|-
| RAK4631
| 10
|-
| Heltec T114
| 8
|}

If unsure, use <code>8</code> as a safe value.

-----

<span id="step-5-select-the-firmware-file"></span>
=== Step 5 — Select the firmware file ===

In the '''nRF Device Firmware Update''' app:

# Select the firmware ZIP file you downloaded.
# Scan for nearby DFU devices.
# Select the repeater.

The device may appear as a DFU device rather than by its normal MeshCore name.

If the device does not appear:

* Make sure Bluetooth is enabled.
* Move closer to the repeater.
* Re-run the MeshCore command: <code>start ota</code>
* Try enabling '''Force Scanning''' in the DFU app if available.
* Toggle Bluetooth off and on.
* Restart the phone if needed.

-----

<span id="step-6-start-the-upload"></span>
=== Step 6 — Start the upload ===

Press '''Upload''' in the DFU app.

Keep the phone awake and close to the repeater until the update finishes.

Do not:

* Leave the app.
* Lock the phone.
* Walk away from the repeater.
* Turn Bluetooth off.
* Power off the repeater.

The update can take a few minutes.

-----

<span id="step-7-wait-for-reboot"></span>
=== Step 7 — Wait for reboot ===

When the upload completes, the repeater should reboot automatically.

Wait a minute or two before trying to reconnect.

-----

<span id="step-8-confirm-the-upgrade"></span>
=== Step 8 — Confirm the upgrade ===

Reconnect to the repeater in the MeshCore app.

Check the firmware version from the management screen or command line.

Also check that the repeater settings are still correct, especially:

* Region / scope settings
* Default scope
* Repeater enabled
* Advert settings
* Flood settings
* TX power
* Admin access
* GPS/location settings if used

-----

<span id="method-2-ota-update-for-esp32-devices"></span>
== Method 2: OTA update for ESP32 devices ==

Use this method for ESP32-based MeshCore repeaters or room servers.

-----

<span id="step-1-connect-to-the-repeater-in-meshcore"></span>
=== Step 1 — Connect to the repeater in MeshCore ===

# Open the MeshCore app.
# Connect to the repeater or room server.
# Log in using the admin password.
# Open the repeater command line / terminal.

-----

<span id="step-2-start-ota-mode"></span>
=== Step 2 — Start OTA mode ===

Enter the following command:

<code>start ota</code>

The ESP32 device should start a temporary Wi-Fi access point called something like:

<code>MeshCore OTA</code>

-----

<span id="step-3-connect-to-the-ota-wi-fi"></span>
=== Step 3 — Connect to the OTA Wi-Fi ===

On your phone, tablet or laptop:

# Open Wi-Fi settings.
# Connect to the temporary Wi-Fi network:

<code>MeshCore OTA</code>

<ol start="3" style="list-style-type: decimal;">
<li>Stay connected to this Wi-Fi until the upload is complete.</li></ol>

-----

<span id="step-4-open-the-ota-upload-page"></span>
=== Step 4 — Open the OTA upload page ===

Open a web browser and go to:

<code>http://192.168.4.1/update</code>

If the CLI shows a different IP address, use the IP address shown by the device.

-----

<span id="step-5-upload-the-firmware"></span>
=== Step 5 — Upload the firmware ===

# Choose the firmware file.
# Make sure the file is the correct one for your hardware.
# Make sure the filename does '''not''' contain <code>merged</code>.
# Upload the file.
# Wait until the update completes.

Do not disconnect from the <code>MeshCore OTA</code> Wi-Fi while the upload is running.

<blockquote>'''Important:''' Do not use a merged firmware file for ESP32 OTA updates.<br />
A merged firmware file is normally for a full USB flash and may wipe or reset the device.
</blockquote>

-----

<span id="step-6-wait-for-reboot-and-confirm"></span>
=== Step 6 — Wait for reboot and confirm ===

After upload, the device should reboot.

Reconnect through the MeshCore app and confirm:

* Firmware version
* Repeater settings
* Region / scope settings
* Admin access
* TX power
* Advert and flood settings

-----

<span id="scot-mesh-post-upgrade-checks"></span>
== Scot Mesh post-upgrade checks ==

After upgrading a Scot Mesh repeater, check the following before leaving it alone.

<span id="basic-checks"></span>
=== Basic checks ===

* Repeater is online
* Repeater can be seen by nearby nodes
* Admin access still works
* Firmware version is correct
* Time/location information looks correct if used

-----

<span id="region-and-scope-checks"></span>
=== Region and scope checks ===

For Scot Mesh, confirm the repeater still has the correct region configuration.

Typical Scot Mesh structure:

{| class="wikitable"
|-
! Code
! Region
|-
| <code>sco</code>
| Scotland
|-
| <code>cen</code>
| Central Scotland
|-
| <code>fal</code>
| Falkirk
|-
| <code>ioi</code>
| Island of Ireland neighbour region
|}

Check that the repeater has the correct local and parent regions for its area.

Also confirm that wildcard / unrestricted flooding has not been accidentally restored.

-----

<span id="recommended-scot-mesh-settings-to-re-check"></span>
=== Recommended Scot Mesh settings to re-check ===

The exact settings may vary by repeater, but these are worth checking after any firmware upgrade:

* Default scope
* Region list
* Region parent relationships
* Region flood permissions
* Wildcard flood deny
* Repeater enabled
* TX power
* Flood max
* Advert interval
* Flood advert interval
* Path hash size / routing byte size

If the repeater was part of the Scot Mesh scoped region rollout, do not assume these settings survived the upgrade. Check them.

-----

<span id="troubleshooting"></span>
== Troubleshooting ==

<span id="the-repeater-does-not-appear-in-the-dfu-app"></span>
=== The repeater does not appear in the DFU app ===

Try the following:

* Move closer to the repeater.
* Run <code>start ota</code> again.
* Turn Bluetooth off and on.
* Enable '''Force Scanning''' in the DFU app.
* Restart the phone.
* Power-cycle the repeater if safe to do so.

-----

<span id="the-update-stalls"></span>
=== The update stalls ===

Do not immediately power-cycle the repeater.

First:

* Keep the phone close.
* Keep the app open.
* Wait a few minutes.
* Check that Bluetooth or Wi-Fi is still connected.

If it has clearly failed:

* Close the DFU app.
* Toggle Bluetooth off and on.
* Restart the phone if needed.
* Reconnect to the repeater if possible.
* Run <code>start ota</code> again.
* Retry the upload.

-----

<span id="the-phone-locked-during-the-update"></span>
=== The phone locked during the update ===

If the update has stopped progressing:

* Unlock the phone.
* Return to the DFU app.
* Check whether the upload resumes.

If it does not resume, restart the OTA process.

For future updates, keep the phone awake and the DFU app in the foreground.

-----

<span id="the-repeater-does-not-come-back-after-ota"></span>
=== The repeater does not come back after OTA ===

Possible causes:

* Wrong firmware file
* Power loss during update
* Bluetooth/Wi-Fi upload failure
* Bootloader issue

Try:

* Wait a few minutes.
* Scan again in the MeshCore app.
* Scan again in the DFU app.
* Power-cycle the repeater if safe.
* Try the OTA process again if the device still appears in DFU mode.

If the device no longer appears in MeshCore or DFU mode, it may need a physical USB recovery flash.

-----

<span id="good-practice"></span>
== Good practice ==

Before updating an important repeater:

* Update one test device first.
* Keep a copy of the old known-good firmware.
* Take screenshots of important settings.
* Avoid updating multiple key repeaters at the same time.
* Avoid updating during poor weather if solar powered.
* Avoid updating when the network is busy.
* Tell local users before upgrading a major repeater.

For hilltop or difficult-access repeaters, consider fitting or confirming an OTA-capable bootloader before deployment.

-----

<span id="summary"></span>
== Summary ==

The normal OTA process is:

# Download the correct firmware.
# Connect to the repeater as admin.
# Open the command line.
# Run <code>start ota</code>.
# Use the DFU app for nRF52 devices.
# Use the MeshCore OTA Wi-Fi page for ESP32 devices.
# Wait for reboot.
# Confirm firmware and settings.

OTA makes repeater maintenance much easier, but always check the firmware file and confirm the repeater settings afterwards.

MeshCore/FAQ

2026-11-03T17:06:27Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:FAQ}}
<span id="meshcore-faq"></span>
== MeshCore FAQ 🙋 ==

Quick answers to the questions that come up most often. If yours is not here, ask on [https://discord.gg/ytxfyuDmSt Discord].

-----

<span id="do-i-need-a-radio-licence-to-use-meshcore"></span>
=== Do I need a radio licence to use meshcore? ===

No. MeshCore uses licence-exempt LoRa frequencies (868 MHz in the UK). Anyone can carry a companion node and use the app. No amateur radio licence required.

-----

<span id="what-is-the-range"></span>
=== What is the range? ===

It depends heavily on where you are and whether there is a repeater nearby. A companion node in the open might reach a couple of kilometres to a nearby repeater. A well-sited repeater on a hill can cover tens of kilometres. In a city with buildings in the way, range is shorter.

Currently our distance record across water is '''160km from Galloway to Dublin.'''

Our record across land is '''120km from Angus down to SOuth Lanark.'''

-----

<span id="why-cant-i-hear-anyone"></span>
=== Why can’t I hear anyone? ===

A few things to check, in order:

# '''Scope is wrong.''' The most common cause. Go to '''Experimental Settings''' in the app and confirm '''Default Scope Region''' is set to <code>sco</code>. Then check the channel scope too — see [[MeshCore/Scopes|Scopes]].
# '''No repeater nearby.''' Use '''Tools → Repeater Scanner''' in the MeshCore app to scan for nearby ScotMesh repeaters, then wait for the scan to complete and confirm that local repeaters are being discovered.
# '''Wrong radio preset.''' Make sure your device is flashed with the '''EU/UK (Narrow)''' preset. A device on the wrong channel or spreading factor will not hear anything.
# '''Device not transmitting.''' Try <code>#test</code> with scope <code>sco</code> — you should at least see your own message go out.

If you have checked all of the above and still hear nothing, ask on [https://discord.gg/ytxfyuDmSt Discord].

-----

<span id="what-is-the-difference-between-a-channel-and-a-scope"></span>
=== What is the difference between a channel and a scope? ===

* A '''channel''' is a named group chat — <code>#scotland</code>, <code>#glasgow</code>, <code>#test</code>. It is just a label for people.
* A '''scope''' is a region code that repeaters use to decide whether to carry your message — <code>sco</code>, <code>gla</code>, <code>edi</code>.

You can send a message on <code>#glasgow</code> with the scope set to <code>sco</code> and it will go Scotland-wide. Or you can set the scope to <code>gla</code> and it will only travel through Glasgow-area repeaters. The channel name does not change that — the scope does. See [[MeshCore/Scopes|Scopes]] for the full explanation.

-----

<span id="why-is-the-wildcard-not-allowed"></span>
=== Why is the <code>*</code> wildcard not allowed? ===

The <code>*</code> wildcard tells repeaters to forward everything to everyone. On a well-grown network that floods the airtime with traffic that most people do not need. ScotMesh uses deliberate region scopes instead — set <code>sco</code> for Scotland-wide, <code>gla</code> for Glasgow, and so on — so traffic only travels where it is actually useful.

<blockquote>In late March / early April 2026, the ScotMesh MC network officially formed when West Coast repeaters successfully linked with East Coast repeaters. This gave us around two weeks of reliable country-wide messaging across Scotland, proving that the network could work well as a connected Scottish mesh.The situation changed when our Galloway repeater linked us into Ireland and, through that path, to the remainder of the wider UK mesh. While wider interconnection may sound positive, in practice it created a major problem for ScotMesh. The network was suddenly exposed to a very high level of uncontrolled flood traffic, estimated at around 24,000 flood packets per day, plus around 600 public messages being present. Much of this traffic was unnecessary for Scottish users and included political arguments, off-topic content, and various abusive or inappropriate remarks.
This level of uncontrolled traffic had a damaging effect on ScotMesh. It increased congestion, reduced the reliability of useful local messaging, and made the network harder to manage. This was the reason ScotMesh moved towards a clearer regional framework, allowing Scotland to remain connected where appropriate while keeping routine traffic scoped, relevant, and manageable. This is also the reason why are unlikely to ever allow wildcard flooding again.
</blockquote>
There is one exception: <code>*</code> is used as a root parent in repeater configuration commands (for example <code>region put sco *</code>). That is a region tree concept, not wildcard forwarding. See [[MeshCore/Regions|Regions]] for the detail.

-----

<span id="can-i-use-scotmesh-without-a-repeater-nearby"></span>
=== Can I use ScotMesh without a repeater nearby? ===

Yes, but your range is very limited. Two companion nodes in line of sight can talk directly. If there is no repeater between you and another user, messages will only reach as far as direct radio range allows — often just a few hundred metres in built-up areas.

If you want to extend coverage in your area, the best thing to do is put up a repeater. See [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]].

-----

<span id="what-device-should-i-buy"></span>
=== What device should I buy? ===

The [https://meshcore.io/flasher MeshCore Flasher] lists devices that can be flashed with MeshCore firmware — that is a good starting point for what is currently supported. Popular choices include boards from Heltec, LilyGo, and RAK, but the community’s preferences do shift as new hardware comes out.

The best thing to do is ask on [https://discord.gg/ytxfyuDmSt Discord] — someone will point you at whatever is working well right now.

-----

<span id="how-do-i-know-if-my-device-is-working"></span>
=== How do I know if my device is working? ===

Send a message on <code>#test</code> with scope <code>sco</code>. If you can see the message appear in the app after sending, the device is transmitting. If someone else on the network responds, you have confirmed two-way comms.

Use '''Tools → Repeater Scanner''' in the MeshCore app to scan for nearby ScotMesh repeaters, then wait for the scan to complete and confirm that local repeaters are being discovered.

-----

<span id="do-i-need-to-set-scope-for-every-channel-separately"></span>
=== Do I need to set scope for every channel separately? ===

Not necessarily. If you set a '''default scope''' of <code>sco</code> in Experimental Settings, that applies to any channel that does not have its own scope override. You only need to set a per-channel scope when you want something different — for example <code>gla</code> on <code>#glasgow</code> to keep traffic local, or <code>ioi</code> on <code>#ireland</code> for the Island of Ireland path. See [[MeshCore/Scopes|Scopes]] for the full detail.

-----

<span id="what-is-the-island-of-ireland-ioi-scope"></span>
=== What is the Island of Ireland (<code>ioi</code>) scope? ===

ScotMesh and the Irish MeshCore community have a peering agreement. Repeaters on both sides carry the <code>ioi</code> scope so that traffic can move between the two networks in a controlled way — without flooding everything. You can join <code>#ireland</code> and set scope to <code>ioi</code> to talk on that path. See [[MeshCore/Channels|Channels]] for more.

-----

<span id="something-else-not-answered-here"></span>
=== Something else not answered here? ===

Jump on [https://discord.gg/ytxfyuDmSt Discord] — the community is friendly and happy to help.

MeshCore/Observers

2026-11-03T17:06:24Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:Observers}}
<span id="meshcore-observers"></span>
== MeshCore Observers ==

Observers are how ScotMesh nodes appear on the live map. An '''MQTT observer''' build is a repeater-style MeshCore firmware image that can push mesh traffic up to one or more '''MQTT''' brokers — feeding live maps and tools — without replacing the normal RF repeater role. You can also run a receive-only observer at a site that does not repeat on air.

For the full technical detail on the bridge (up to three broker slots, presets, <code>custom</code>, JWT <code>audience</code>, merged first flash, and more), see the upstream write-up: [https://github.com/agessaman/MeshCore/blob/mqtt-bridge-implementation-flex/MQTT_IMPLEMENTATION.md MQTT_IMPLEMENTATION.md (agessaman fork)].

<span id="firmware"></span>
=== Firmware ===

Prebuilt '''repeater observer MQTT''' binaries are published here:

https://static.loraproject.ie/mqtt/

Pick the file that matches your '''exact board''' (Heltec, LilyGo, RAK, Station G2, and others appear in the directory listing).

'''<code>*_merged.bin</code> vs the non-merged <code>.bin</code>'''

* '''Files ending in <code>_merged.bin</code>''' are a '''full''' image (bootloader, partition table, and application). Flashing one '''normally wipes''' stored repeater settings). Use merged when you '''need''' that full layout refresh—for example the '''first''' move to observer firmware on a board, or when the observer build’s '''partition table''' is new for that hardware (see “Partition Table Changes” in [https://github.com/agessaman/MeshCore/blob/mqtt-bridge-implementation-flex/MQTT_IMPLEMENTATION.md MQTT_IMPLEMENTATION.md]).
* '''Files without <code>_merged</code> in the name''' update the '''app''' only when the '''partition layout is unchanged'''. That path is what you want when you '''already run observer firmware or a repeater''' on that board and you want to '''keep''' your current configuration through an upgrade.

After a merged flash, '''re-enter''' RF settings, node name, Wi‑Fi, MQTT, <code>mqtt.iata</code>, and other stored values. After a non-merged upgrade on the same layout, settings are '''usually''' kept—still read release notes. Later updates can use '''OTA''' ([[#updates-without-usb-start-ota|<code>start ota</code>]]) or a non-merged binary when appropriate.

<span id="updates-without-usb-start-ota"></span>
=== Updates without USB: <code>start ota</code> ===

On the repeater '''serial console''' (same place you run <code>set</code> / <code>get</code> commands), you can start the '''over-the-air''' path that brings up Wi‑Fi for firmware upload, so you do not have to plug in USB for every update. The exact command is:

<syntaxhighlight lang="text">start ota</syntaxhighlight>
Use your build’s normal OTA workflow (browser or tool) once the device is advertising the update Wi‑Fi. Keep power stable during the flash.

<span id="observer-setup"></span>
=== Observer setup ===

# '''Flash''' the <code>*repeater_observer_mqtt*</code> file for your board ([[#firmware|Firmware]] explains '''<code>_merged.bin</code>''' vs non-merged).
# '''If NVS was wiped''' (typical after '''<code>_merged.bin</code>'''; '''NVS''' is ''Non-Volatile Storage''—flash-backed settings such as Wi‑Fi, MQTT, and radio prefs), set '''RF and node identity''' first: frequency, bandwidth, SF, CR, TX power, and '''name''' must match your mesh before the node is useful on air. Use the '''device web UI''' or admin screens, or serial, using your coordinator’s values; repeater planning is in [[MeshCore/Regions|Regions]]. '''Then''' work through '''Wi‑Fi''' → '''<code>mqtt.iata</code>''' → (optional '''receive-only''') → '''MQTT''' in order below. '''If you used a non-merged''' update and kept settings, use <code>get</code> and only redo what is wrong—but '''still check MQTT''': stock images often leave '''LetsMesh Analyzer US''' on '''slot 1''' and '''LetsMesh Analyzer EU''' on '''slot 2''' until you repoint them (for example MayoMesh on slot 1).

<span id="wifi"></span>
==== Wi‑Fi ====

The observer needs LAN or internet path to the broker.

<syntaxhighlight lang="text">set wifi.ssid YourWiFiNetwork
set wifi.pwd YourWiFiPassword</syntaxhighlight>
<span id="site-code-mqtt.iata"></span>
==== Site code (<code>mqtt.iata</code>) ====

A short tag for '''where the repeater sits'''. It appears in MQTT topics and on maps—pick something stable (IATA-style codes are common).

{| class="wikitable"
|-
! Code
! Area
|-
| <code>EDI</code>
| Edinburgh
|-
| <code>DND</code>
| Dundee
|-
| <code>GLA</code>
| Glasgow
|}

<syntaxhighlight lang="text">set mqtt.iata EDI</syntaxhighlight>
<span id="optional-receive-only-on-rf"></span>
==== Optional: receive-only on RF ====

If this unit should '''not''' relay mesh traffic on air:

<syntaxhighlight lang="text">set repeat off</syntaxhighlight>
<span id="mqtt-mayomesh-on-slot-1"></span>
==== MQTT (MayoMesh on slot 1) ====

ScotMesh uses '''MayoMesh''' for the shared observer map and broker (who runs it and links: [[#mayomesh-live-map|MayoMesh live map]]). Observer builds usually ship with '''LetsMesh Analyzer US''' on '''slot 1''' and '''LetsMesh Analyzer EU''' on '''slot 2'''. Point '''slot 1''' at MayoMesh for our map. '''Apply this whenever <code>get mqtt1.preset</code> is not already your MayoMesh custom setup'''—including after a merged flash '''and''' after a non-merged upgrade from stock observer images.

<syntaxhighlight lang="text">set mqtt1.preset custom
set mqtt1.server mqtt.mayomesh.net
set mqtt1.port 443
set mqtt1.audience mqtt.mayomesh.net</syntaxhighlight>
If you '''only''' use MayoMesh and want to free a second TLS slot on low-RAM boards (see upstream notes on PSRAM / two WSS connections):

<syntaxhighlight lang="text">set mqtt2.preset none</syntaxhighlight>
Then:

<syntaxhighlight lang="text">reboot</syntaxhighlight>
With '''<code>audience</code>''' set, the device uses '''JWT (Ed25519)''' sign-in to the broker, same idea as the built-in WSS presets in [https://github.com/agessaman/MeshCore/blob/mqtt-bridge-implementation-flex/MQTT_IMPLEMENTATION.md MQTT_IMPLEMENTATION.md].

<span id="check"></span>
==== Check ====

<syntaxhighlight lang="text">get mqtt.status
get mqtt1.preset
get mqtt.tx
get mqtt.rx</syntaxhighlight>
Confirm the node shows on [https://meshcore.mayomesh.net/ meshcore.mayomesh.net] after a short wait.

<span id="mayomesh-live-map"></span>
=== MayoMesh live map ===

* '''Who runs it:''' MayoMesh (the map and <code>mqtt.mayomesh.net</code> broker) is operated by '''County Mayo''', '''Ireland'''. ScotMesh uses that community’s infrastructure for the shared observer map.
* '''LetsMesh Analyzer:''' [https://analyzer.letsmesh.net/packets?region=EDI,DND,DUB,BHD,GLA packet view filtered to <code>EDI</code>, <code>DND</code>, <code>DUB</code>, <code>BHD</code>, <code>GLA</code>].
* '''MayoMesh live map:''' [https://meshcore.mayomesh.net/ meshcore.mayomesh.net] — MQTT over WebSocket (for example <code>wss://mqtt.mayomesh.net</code>, as shown on the site).
* '''Broker commands''' for your repeater are in [[#observer-setup|Observer setup]] under '''MQTT (MayoMesh on slot 1)'''.
* '''Self-hosting the map UI:''' based on [https://github.com/yellowcooln/meshcore-mqtt-live-map yellowcooln/meshcore-mqtt-live-map]; point your instance at MayoMesh’s broker instead of default LetsMesh-style endpoints.

<span id="mqtt-uplink-mqtt.tx-advert-vs-on"></span>
=== MQTT uplink: <code>mqtt.tx</code> advert vs <code>on</code> ===

These control '''which of this node’s transmitted packets''' are sent upstream over MQTT. '''<code>mqtt.rx</code>''' is separate (received packets).

{| class="wikitable"
|-
! Setting
! Effect
|-
| <code>set mqtt.tx advert</code>
| Uplink '''only this node’s own advert''' TX packets. Lighter load; usually enough for map presence.
|-
| <code>set mqtt.tx on</code>
| Uplink '''all TX''' from this node. Richer feed, more bandwidth and airtime.
|-
| <code>set mqtt.tx off</code>
| No TX uplink over MQTT.
|}

For most map feeds, '''<code>advert</code>''' is enough:

<syntaxhighlight lang="text">set mqtt.tx advert</syntaxhighlight>
If you need every TX packet this node sends mirrored upstream:

<syntaxhighlight lang="text">set mqtt.tx on</syntaxhighlight>
Use '''<code>on</code>''' only when you intend that heavier feed (more bandwidth and airtime).
## 🔗 See also

* [[MeshCore/Regions|Regions]] — repeater region codes on the Scottish mesh.
* [[MeshCore|MeshCore]] — hub page for channels, scopes, and related guides.

MeshCore/Repeater Quick Setup

2026-11-03T17:06:22Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:Repeater Quick Setup}}
<span id="meshcore-repeater-quick-setup"></span>
== MeshCore Repeater Quick Setup ==

This is the short version for setting up a MeshCore repeater on ScotMesh.

A repeater helps the network by hearing MeshCore traffic and passing it on. A good repeater in a good location can make a big difference for everyone nearby.

<div class="sm-cx sm-cx-warning">

ScotMesh does not use wildcard forwarding.

Add the right regions, allow those regions, and deny wildcard forwarding with <code>region denyf *</code>.

</div>
<span id="quick-settings"></span>
=== Quick settings ===

{| class="wikitable"
|-
! Setting
! Use
|-
| Configurator
| MeshCore web flasher: <code>https://meshcore.io/flasher</code>
|-
| Preset
| EU/UK (Narrow)
|-
| Device role
| Repeater
|-
| Browser
| Chrome or Edge
|-
| Baseline regions
| <code>sco</code>, <code>ioi</code>
|-
| Local regions
| Add only the areas the repeater genuinely serves
|-
| Wildcard forwarding
| Deny with <code>region denyf *</code>
|-
| Flood advert interval
| 24 hours
|-
| Default scope
| <code>sco</code> — '''required''' so other repeaters accept your adverts
|}

<span id="before-you-start"></span>
=== Before you start ===

You will need:

* A supported LoRa device — open the [https://meshcore.io/flasher MeshCore Flasher] to see what can be flashed, or ask on [https://discord.gg/ytxfyuDmSt Discord].
* A USB data cable, not a charge-only cable.
* A laptop or desktop with Chrome or Edge.
* A sensible repeater location.
* Reliable power.

<div class="sm-cx sm-cx-info">

Location matters more than almost anything else.

A modest repeater in a high, clear spot is usually more useful than a powerful setup hidden indoors.

</div>
<span id="choose-your-region-settings"></span>
=== Choose your region settings ===

Start with <code>sco</code> and <code>ioi</code>, then add the local areas the repeater genuinely covers.

{| class="wikitable"
|-
! Location / coverage
! Regions to add
! Notes
|-
| Any Scottish repeater
| <code>sco</code>, <code>ioi</code>
| Baseline ScotMesh setup.
|-
| Fife
| <code>sco</code>, <code>ioi</code>, <code>fif</code>
| Fife-wide coverage.
|-
| Central Scotland
| <code>sco</code>, <code>ioi</code>, <code>cen</code>
| Wider Central belt coverage.
|-
| Falkirk
| <code>sco</code>, <code>ioi</code>, <code>cen</code>, <code>fal</code>
| Falkirk local coverage.
|-
| Edinburgh area
| <code>sco</code>, <code>ioi</code>, <code>cen</code>, <code>edi</code>
| Edinburgh-facing Central Scotland coverage.
|-
| Glasgow area
| <code>sco</code>, <code>ioi</code>, <code>cen</code>, <code>gla</code>
| Glasgow-facing Central Scotland coverage.
|-
| Tayside
| <code>sco</code>, <code>ioi</code>, <code>tay</code>
| Wider Tayside coverage.
|-
| Dundee area
| <code>sco</code>, <code>ioi</code>, <code>tay</code>, <code>dun</code>
| Dundee local coverage.
|-
| Perth area
| <code>sco</code>, <code>ioi</code>, <code>tay</code>, <code>per</code>
| Perth local coverage.
|-
| High site / bridge
| <code>sco</code>, <code>ioi</code>, plus genuinely served areas
| Do not add every region just because it is listed.
|}

<span id="simple-setup-flow"></span>
=== Simple setup flow ===

# Open the MeshCore web flasher in Chrome or Edge.
# Select your device.
# Choose the repeater role.
# Use the EU/UK (Narrow) preset.
# Flash the device with the latest stable firmware
# Set a clear repeater name.
# Add the right regions from the table above.
# Set flood adverts to 24 hours.
# Deny wildcard forwarding.
# Set <code>region default sco</code>.
# Save the region configuration.

<span id="simple-command-examples"></span>
=== Simple command examples ===

<span id="baseline-scottish-repeater"></span>
==== Baseline Scottish repeater ====

Use this when the repeater is part of ScotMesh but does not have a more specific local region yet.

<syntaxhighlight lang="text">region put sco *
region put ioi *

region allowf sco
region allowf ioi

region denyf *

set flood.advert.interval 24

region default sco

region save</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

Without <code>region default sco</code>, your repeater’s adverts are sent unscoped. The Scottish network denies unscoped forwarding (<code>region denyf *</code>), so other repeaters will reject those adverts and will not know your repeater is there.

</div>
<span id="fife-repeater"></span>
==== Fife repeater ====

Use this when the repeater serves Fife.

<syntaxhighlight lang="text">region put sco *
region put ioi *
region put fif sco

region allowf sco
region allowf ioi
region allowf fif

region denyf *

set flood.advert.interval 24

region default sco

region save</syntaxhighlight>
<span id="central-scotland-falkirk-repeater"></span>
==== Central Scotland / Falkirk repeater ====

Use this when the repeater serves Falkirk and wider Central Scotland.

<syntaxhighlight lang="text">region put sco *
region put ioi *
region put cen sco
region put fal cen

region allowf sco
region allowf ioi
region allowf cen
region allowf fal

region denyf *

set flood.advert.interval 24

region default sco

region save</syntaxhighlight>
<span id="good-repeater-habits"></span>
=== Good repeater habits ===

* Put the repeater as high and clear as you reasonably can.
* Use stable power.
* Keep the antenna vertical.
* Give the repeater a name people can recognise.
* Add only the regions it genuinely serves.
* Use <code>region denyf *</code>; do not allow wildcard forwarding.
* Set <code>region default sco</code> so your adverts are accepted by the rest of the mesh.
* Set flood adverts to 24 hours.
* Ask the community before inventing new region codes.

<span id="where-to-go-next"></span>
=== Where to go next ===

* [[MeshCore/Regions|Regions]] has the fuller region guide and more command examples.
* [[MeshCore/Scopes|Scopes]] explains what Companion App users need to set.
* [[MeshCore/Channels|Channels]] lists the agreed and proposed channels.
* [https://docs.meshcore.io/cli_commands/ MeshCore CLI Commands] is the upstream command reference.

<span id="appendix-what-the-key-commands-mean"></span>
=== Appendix: what the key commands mean ===

{| class="wikitable"
|-
! Command
! Meaning
|-
| <code>region put sco *</code>
| Create <code>sco</code> at the top of the region tree.
|-
| <code>region put fif sco</code>
| Create <code>fif</code> as a child of <code>sco</code>.
|-
| <code>region allowf sco</code>
| Allow scoped flood traffic for <code>sco</code>.
|-
| <code>region denyf *</code>
| Deny unscoped wildcard forwarding.
|-
| <code>set flood.advert.interval 24</code>
| Set flood adverts to 24 hours.
|-
| <code>region default sco</code>
| Set the default scope so adverts from this repeater are scoped to <code>sco</code> and accepted by the mesh.
|-
| <code>region save</code>
| Save the region configuration.
|}

MeshCore/Regions

2026-11-03T17:06:17Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:Regions}}
<span id="meshcore-regions"></span>
== MeshCore Regions ==

-----

<blockquote><span id="note---a-regional-framework-was-impelemented-in-the-scotmesh-meshcore-mesh-at-the-beginning-of-april-2026.-this-was-out-of-sheer-necessity-as-our-mesh-was-dying-under-the-flood-traffic-from-england-24000-flood-packets-600-messages-daily.-this-saved-our-mesh-from-descending-into-a-chaotic-unusable-mess-of-incoherent-rambles-and-frustrated-messaging-failures.-this-is-why-an-understaning-of-regions-is-imperative-to-understanding-where-we-are-today"></span>
==== NOTE - A Regional Framework was impelemented in the ScotMesh Meshcore Mesh at the beginning of April 2026. This was out of sheer necessity as our mesh was dying under the flood traffic from England (24,000 flood packets & 600+ messages daily). This saved our mesh from descending into a chaotic, unusable mess of incoherent rambles and frustrated messaging failures. This is why an understaning of regions is imperative to understanding where we are today ====
</blockquote>

-----

This guide is for '''repeater owners'''.

The aim is simple: keep the scheme readable, predictable, and usable as the network grows.

<span id="why-regions-are-needed"></span>
=== Why regions are needed ===

MeshCore messages travel through repeaters for onward routing. Whilst this is the core function, if every repeater carries every message everywhere, the network becomes noisy, inefficient and flooded with uneccessary traffic.

Regions help us:

# '''Keep local traffic local'''<br />
In the future, a message that only matters in one area wont always need to be repeated across every part of Scotland.
# '''Reduce unnecessary radio traffic'''<br />
LoRa is subject to a finite airtime cycle per hour (compared with Wi-Fi or mobile data), so every avoidable repeat uses valuable airtime.
# '''Improve reliability'''<br />
Less unnecessary repeating leaves more room for useful messages.
# '''Make planning clearer'''<br />
Regions make repeater deployment easier to map, identify needs, plan future expansion and ease of ongoing mesh maintenance.
# '''Support controlled peering'''<br />
Strategic repeaters can deliberately carry neighbouring traffic, such as the '''IOI peering agreement''' between Scotland and the Island of Ireland.

<span id="regions-and-scopes"></span>
=== Regions and scopes ===

There are two related concepts: '''regions''' and '''scopes'''.

{| class="wikitable"
|-
! Term
! Meaning
! Example
|-
| '''Region'''
| A label configured on a repeater to describe the area it serves.
| An Edinburgh-area repeater includes <code>edi</code>.
|-
| '''Scope'''
| A label applied to messages or channels to describe which area (or region) the traffic is intended to travel.
| The <code>#glasgow</code> channel might use <code>gla</code> when traffic should stay in that area.
|}

In a densely populated mesh, a repeater should only carry scoped traffic for regions it genuinely serves. In new or embryonic meshes, this requirment will be a future need but best practise planning mandates introducing regions as early as is practical.

<span id="wildcard-forwarding-is-not-allowed-see-info-box-at-top-of-this-document-for-context."></span>
=== Wildcard forwarding is not allowed (see info box at top of this document for context). ===

The wildcard marker is:

<syntaxhighlight lang="text">*</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

The important rule is: <code>*</code> will appear as a root parent in the region tree, but wildcard forwarding must be denied.

In other words, <code>region put sco *</code> is correct, but must be preceeded by <code>region denyf *</code> .

</div>
The Scottish MeshCore setup does not allow wildcard forwarding. Repeater owners must deny wildcard forwarding with:

<syntaxhighlight lang="text">region denyf *</syntaxhighlight>
You may still see <code>*</code> as the root parent when defining the region tree, for example <code>region put sco *</code>. That is different from allowing wildcard forwarding.

For channel names and suggested scopes, see [[MeshCore/Channels|Channels]].

<span id="scottish-region-code-approach"></span>
=== Scottish region code approach ===

For Scotland, we use simple three-letter lowercase codes.

We are not part of any UK wide mesh (for context see comment box at the top of this documnet) Therefore, '''we are not using any long prefixed names'''

We use short codes such as:

<syntaxhighlight lang="text">sco
cen
fal</syntaxhighlight>
Other countries and communities may use ISO-style hierarchical codes. That is valid for them, but the Scottish convention is designed to be short and easy to read in apps, analyser tools, and community discussions.

<span id="current-june-2026-agreed-region-codes"></span>
=== Current (June 2026) Agreed region codes ===

{| class="wikitable"
|-
! Code
! Area
|-
| <code>sco</code>
| Scotland
|-
| <code>cen</code>
| Central Scotland
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>gla</code>
| Glasgow area
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>dun</code>
| Dundee area
|-
| <code>per</code>
| Perth area
|-
| <code>ang</code>
| Angus area
|-
| <code>ioi</code>
| Island of Ireland (<code>ioi</code>) — IOI peering
|}

<span id="ioi-peering-agreement"></span>
=== IOI peering agreement ===

The Scottish and Irish MeshCore communities maintain a '''peering agreement''': scoped traffic is carried on the other network only where '''both''' sides configure for it.

Under that agreement, Scottish repeaters add the <code>ioi</code> region alongside <code>sco</code> where the Scottish baseline applies, and Island of Ireland repeaters add <code>sco</code> alongside their own region codes in the same spirit. Messages with matching '''scopes''' can then move between the two networks predictably, without relying on wildcard forwarding. For example channel names and typical scopes, see [[MeshCore/Channels|Channels]].

The <code>ioi</code> code is '''not''' a Scottish local region. It marks repeaters and traffic that deliberately participate in that peering.

Do not use:

<syntaxhighlight lang="text">ioi-sco</syntaxhighlight>
Use:

<syntaxhighlight lang="text">ioi</syntaxhighlight>
<span id="peering-with-scotland-other-regions"></span>
==== Peering with Scotland (other regions) ====

If another region wants to peer with Scotland in a similar way, they should already have the following in place:

# '''Wildcard flooding disallowed''' on their repeaters (the same principle as the Scottish setup: deny wildcard forwarding with <code>region denyf *</code>; see [[#wildcard-forwarding-is-not-allowed|Wildcard forwarding is not allowed]]).
# '''Appropriate regions on their repeaters''' so traffic is not forwarded wider than intended, and Scottish repeaters are not flooded with scoped traffic they did not agree to carry.
# '''Neighbouring Scotland in RF terms''' so equipment can '''directly''' peer, rather than assuming long unofficial relay chains.

When that fits your situation, contact the Scottish Mesh community on [https://discord.gg/ytxfyuDmSt Discord] so we can discuss scope names, boundaries, and a safe rollout.

<span id="recommended-hierarchy"></span>
=== Recommended hierarchy ===

Although the hierarchy is not written into the code itself, it can be thought of like this:

<syntaxhighlight lang="text">sco
cen
fal
edi
gla
fif
tay
dun
per
ang
ioi</syntaxhighlight>
In plain English:

* <code>sco</code> is for Scotland-wide traffic.
* <code>tay</code>, <code>cen</code>, and <code>fif</code> are Scottish sub regions.
* <code>fal</code>, <code>edi</code>, <code>gla</code>, <code>dun</code>, <code>per</code> and <code>ang</code> are local areas.
* <code>ioi</code> is for the Island of Ireland under the IOI peering agreement.

<span id="suggested-repeater-configuration-policy"></span>
=== Suggested repeater configuration policy ===

A Scottish repeater should normally be configured with:

# The country code <code>sco</code>.
# The <code>ioi</code> code for IOI peering.
# The relevant regional code.
# The relevant local code, if appropriate.
# Any neighbouring codes that the repeater genuinely serves.

<div class="sm-cx sm-cx-warning">

Do not allow wildcard forwarding.

In command line interface (CLI) examples, this means using <code>region denyf *</code>

</div>
<span id="falkirk-central-scotland-repeater"></span>
==== Falkirk / Central Scotland repeater ====

A repeater covering the Falkirk area would usually have:

<syntaxhighlight lang="text">sco
ioi
cen
fal</syntaxhighlight>
<span id="edinburgh-facing-central-scotland-repeater"></span>
==== Edinburgh-facing Central Scotland repeater ====

A repeater that mainly serves Central Scotland but has strong coverage towards Edinburgh might use:

<syntaxhighlight lang="text">sco
ioi
cen
edi</syntaxhighlight>
<span id="fife-repeater"></span>
==== Fife repeater ====

A Fife repeater would usually have:

<syntaxhighlight lang="text">sco
ioi
fif</syntaxhighlight>
If it genuinely provides useful Central Scotland coverage, it may also include:

<syntaxhighlight lang="text">cen</syntaxhighlight>
<span id="scottish-repeaters-and-ioi"></span>
==== Scottish repeaters and <code>ioi</code> ====

Scottish repeaters should normally include <code>ioi</code> alongside <code>sco</code> as part of the [[#ioi-peering-agreement|IOI peering agreement]]:

<syntaxhighlight lang="text">sco
ioi</syntaxhighlight>
That keeps peering-capable forwarding available where the Scottish baseline is configured. It does not make <code>ioi</code> a Scottish local region.

<span id="good-practice-for-repeater-owners"></span>
=== Good practice for repeater owners ===

Use lowercase region codes. Do not use mixed case such as <code>SCO</code>, <code>Cen</code>, or <code>FAL</code>.

Use agreed codes. For example, use <code>edi</code> for the Edinburgh area, not <code>edn</code>, <code>edinburgh</code>, or <code>gb-edi</code>.

Add only the areas your repeater genuinely serves. A high-site repeater may reasonably serve several areas, but a repeater should not claim every region just because it can occasionally hear distant nodes.

Coordinate before adding new codes. If a new area needs a code, discuss it publicly before using it so that the community does not end up with competing names for the same place.

<span id="suggested-command-examples"></span>
=== Suggested command examples ===

The exact method may vary depending on firmware version and whether you are using the app, web configurator, USB serial, or remote administration. The upstream reference is the MeshCore [https://docs.meshcore.io/cli_commands/ CLI Commands] documentation, especially the region management commands.

<div class="sm-cx sm-cx-info">

New to repeater setup?

Start with [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]], then come back here for the fuller detail.

</div>
For a Central Scotland / Falkirk repeater, the setup may look conceptually like this:

<syntaxhighlight lang="text">region put sco *
region put ioi *
region put cen sco
region put fal cen

region allowf sco
region allowf ioi
region allowf cen
region allowf fal

region denyf *

region default sco

region save</syntaxhighlight>
Then check the result with:

<syntaxhighlight lang="text">region</syntaxhighlight>
For a Tayside / Dundee repeater:

<syntaxhighlight lang="text">region put sco *
region put ioi *
region put tay sco
region put dun tay

region allowf sco
region allowf ioi
region allowf tay
region allowf dun

region denyf *

region default sco

region save</syntaxhighlight>
For a Glasgow-area repeater:

<syntaxhighlight lang="text">region put sco *
region put ioi *
region put gla sco

region allowf sco
region allowf ioi
region allowf gla

region denyf *

region default sco

region save</syntaxhighlight>
For a repeater that serves Scotland, Central Scotland, Glasgow, Edinburgh, and IOI peering (<code>ioi</code>):

<syntaxhighlight lang="text">region put sco *
region put cen sco
region put gla cen
region put edi cen
region put ioi *

region allowf sco
region allowf cen
region allowf gla
region allowf edi
region allowf ioi

region denyf *

region default sco

region save</syntaxhighlight>
On firmware that supports default scope, repeater and room server administrators should also set the default scope for packets that originate from that node:

<syntaxhighlight lang="text">region default sco</syntaxhighlight>
<div class="sm-cx sm-cx-warning">

'''Set <code>region default sco</code> on your repeater.'''

Without a default scope, adverts sent by your repeater go out unscoped. Because the Scottish network uses <code>region denyf *</code>, other repeaters will reject those unscoped adverts and will never learn your repeater exists. Setting the default scope to <code>sco</code> ensures your adverts are carried normally across the mesh.

</div>
This is separate from flood forwarding permissions. For more detail, see [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

Always check for an <code>OK</code> response where applicable, and remember to save the configuration so it survives a reboot.

<span id="firmware-and-app-version-notes"></span>
=== Firmware and app version notes ===

Region and scope support depends on MeshCore firmware and app support.

Use the latest stable MeshCore firmware and app available for your device. Older firmware may still pass some traffic, but region management and scope handling may not behave as expected.

MeshCore region filtering was introduced across firmware and app releases, and default scope support was added later. The MeshCore posts [https://blog.meshcore.io/2026/01/20/region-filtering Region Filtering] and [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region] are useful background when checking version behaviour.

<span id="naming-and-publishing-new-region-codes"></span>
=== Naming and publishing new region codes ===

When a new Scottish area needs a code, use these rules:

# Use three lowercase letters.
# Make the code obvious to local users.
# Avoid clashing with existing agreed codes.
# Avoid overly small areas unless there is a real need.
# Discuss the code with the local MeshCore community before publishing it.

Examples of possible future codes might include:

<syntaxhighlight lang="text">sti = Stirling
liv = Livingston
abe = Aberdeen
inv = Inverness
ayr = Ayrshire
bor = Borders</syntaxhighlight>
These are examples only and should not be treated as agreed until the community confirms them.

<span id="common-questions"></span>
=== Common questions ===

<span id="do-regions-replace-normal-meshcore-messaging"></span>
==== Do regions replace normal MeshCore messaging? ====

No. Regions help control where scoped traffic is repeated.

<span id="should-every-scottish-repeater-have-sco-and-ioi"></span>
==== Should every Scottish repeater have <code>sco</code> and <code>ioi</code>? ====

Yes, that is the recommended baseline for Scottish repeaters. Use <code>sco</code> for Scotland and add <code>ioi</code> alongside it for the IOI peering agreement.

<span id="should-every-repeater-have-every-scottish-region"></span>
==== Should every repeater have every Scottish region? ====

No. That would defeat the purpose of regions. Repeaters should only list the areas they genuinely serve.

<span id="should-we-use-gb-sco-instead-of-sco"></span>
==== Should we use <code>gb-sco</code> instead of <code>sco</code>? ====

Not for this Scottish scheme. Some wider UK or international guides use ISO-style codes, but the local Scottish agreement is to use short three-letter codes.

<span id="can-a-repeater-be-in-more-than-one-region"></span>
==== Can a repeater be in more than one region? ====

Yes. That is useful for high sites, border areas, or repeaters that genuinely link neighbouring areas.

<span id="can-we-allow-for-compatibility"></span>
==== Can we allow <code>*</code> for compatibility? ====

No. The Scottish MeshCore setup does not allow wildcard forwarding. Use the correct region scope instead.

<span id="summary"></span>
=== Summary ===

Regions give the Scottish MeshCore community a simple way to organise the network as it grows.

Our agreed approach is:

* Use three-letter lowercase codes.
* Use <code>sco</code> for Scotland.
* Add <code>ioi</code> wherever the Scottish baseline <code>sco</code> is configured (IOI peering).
* Use <code>cen</code>, <code>tay</code>, <code>gla</code>, and <code>fif</code> for major regions where they match coverage.
* Use <code>fal</code>, <code>edi</code>, <code>gla</code>, <code>dun</code>, and <code>per</code> for local areas.
* Use <code>ioi</code> for Island of Ireland traffic under the IOI peering agreement.
* Deny wildcard forwarding with <code>region denyf *</code>.
* Do not use long prefixes such as <code>gb-sco</code> or <code>sco-fal</code> in this local scheme.

This gives us a clean, readable, and expandable foundation for building a coordinated Scottish MeshCore network.

MeshCore/Channels

2026-11-03T17:06:15Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:Channels}}
<span id="meshcore-channels-now-and-in-the-future"></span>
== MeshCore Channels (now and in the future) ==

Channels are where the conversation happens. Think of them like group chats — anyone with the right device and scope set can join in. There is nothing stopping you creating your own, but the ones below are the agreed community channels so everyone knows where to find each other.

In the Scottish MeshCore network, what really matters for routing is '''region scope''' — not the channel name. The channel name is for people; the scope is for the mesh.

<span id="channel-name-and-scope"></span>
=== 🏷️ Channel name and scope ===

A channel name and a region scope are related, but they are not the same thing.

For example:

<syntaxhighlight lang="text">Channel: #edinburgh
Scope: edi</syntaxhighlight>
The channel name is what you see. The scope is what tells the mesh to carry your message through Edinburgh-area repeaters.

<div class="sm-cx sm-cx-info">

Joining a channel does not automatically set the scope.

Before sending, check the channel settings in the Companion App and make sure the scope matches where you want the message to travel.

</div>
<span id="current-2026-and-proposed-2027-and-beyond-channels"></span>
=== 📡 Current (2026) and proposed (2027 and beyond) channels ===

The following table lists known community channels and proposed channels for Scotland.

'''Type is documentation only; it is not a Companion App setting'''. It groups channels by how you pick them: '''Wide''' for large-footprint traffic (whether the scope is <code>sco</code> or <code>ioi</code>), '''Regional''' for Scottish region area channels, and '''Local''' for Scottish City / town / metropolitan areas. Set '''Scope''' to match the reach you want.

{| class="wikitable"
|-
! Channel
! Type
! Scope
! Status
! Use
|-
| <code>#scotland</code>
| Wide
| <code>sco</code>
| Current
| General Scotland-wide MeshCore traffic.
|-
| <code>#ireland</code>
| Wide
| <code>ioi</code> or <code>sco</code>
| Current
| General Island of Ireland traffic.
|-
| <code>#norniron</code>
| Wide
| <code>ioi</code> or <code>sco</code>
| Current
| Northern Ireland Traffic
|-
| <code>#central</code>
| Regional
| <code>cen</code>
| Proposed
| Central Scotland traffic.
|-
| <code>#dundee</code>
| Local
| <code>dun</code>
| Proposed
| Dundee area traffic.
|-
| <code>#edinburgh</code>
| Local
| <code>edi</code>
| Proposed
| Edinburgh area traffic.
|-
| <code>#falkirk</code>
| Local
| <code>fal</code>
| Proposed
| Falkirk area traffic.
|-
| <code>#fife</code>
| Regional
| <code>fif</code>
| Current
| Fife area traffic.
|-
| <code>#glasgow</code>
| Local
| <code>gla</code>
| Proposed
| Glasgow area traffic.
|-
| <code>#perth</code>
| Local
| <code>per</code>
| Proposed
| Perth area traffic.
|-
| <code>#tayside</code>
| Regional
| <code>tay</code>
| Proposed
| Tayside traffic.
|-
| <code>#test</code>
| Wide
| Set the scope being tested
| Current
| Test messages. Use <code>sco</code>, <code>edi</code>, <code>gla</code>, or another scope that matches what you are testing.
|}

<blockquote>As of Summer 2026, The ScotMesh MC Mesh is still in its early growth phase. As such there is no pressing requirement to restrict in-country traffic to sub regions or local regions. In practical terms country wide traffic will not cause us any issues for at least another year, probably longer. So the country wide region <code>sco</code> will be enough until then.
</blockquote>
Proposed channels are shared names the community is still settling on. They are listed here so that people can talk about the same idea using the same name and scope, rather than ending up with several competing versions.

<span id="choosing-the-right-channel-in-the-future-2027-and-beyond"></span>
=== 🤔 Choosing the right channel in the future (2027 and beyond ===

Use the '''narrowest scope''' that still fits what you are sending. Examples:

<syntaxhighlight lang="text">#scotland / sco Scotland-wide mesh (Current)
#edinburgh / edi Local area (same idea for #glasgow/gla, #fife/fif, #dundee/dun, …)(Future)
#test / <scope> Pick the scope you are actually testing (current)
#ireland / ioi or sco Island of Ireland channel (pick scope for the path you want) (current)</syntaxhighlight>
<span id="good-practice-for-the-future-expanded-mesh"></span>
=== 👍 Good practice for the future expanded mesh ===

* Keep local traffic local where possible.
* Use <code>#test</code> for test messages so normal channels stay readable.
* Use Scotland-wide scope only when the conversation is relevant across Scotland.
* Use <code>ioi</code> when the message belongs on the Island of Ireland scope, or <code>sco</code> on <code>#ireland</code> when you want Scotland-wide scoped carriage (see [[MeshCore/Scopes|Scopes]]).
* Wildcard forwarding will remain disable in the Scottish setup.
* New public channel names tend to land better when discussed with the community first.
* Always check the Companion App scope before sending — a wrong scope and your message goes nowhere useful.

For more detail on setting scope in the Companion App, see [[MeshCore/Scopes|Scopes]]. For repeater and region code guidance, see [[MeshCore/Regions|Regions]]. For '''MQTT observers''' and map uplink, see [[MeshCore/Observers|Observers]].

MeshCore/Scopes

2026-11-03T17:06:13Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:Scopes}}
<span id="meshcore-scopes"></span>
== MeshCore Scopes ==

<div class="sm-cx sm-cx-success">

'''Quick start for most users:''' open the app, go to '''Experimental Settings''', set '''Default Scope Region''' to <code>sco</code>. That is all you need for normal Scottish traffic.

</div>
<div class="sm-cx sm-cx-warning">

'''Watch out:''' if you do not have a suitable '''scope''' set, repeaters on the Scottish MeshCore network wont forward your traffic. You can end up '''shouting into the void'''. Check your default scope and each channel’s scope before you count on messages reaching anyone.

</div>
Scope is the single setting that makes or breaks whether your messages go anywhere on ScotMesh. The channel name is for people — the scope is for the mesh. Set your '''default''' to <code>sco</code>, then adjust per channel when you need something narrower.

<div class="sm-cx sm-cx-info">

'''ScotMesh setup:''' Under '''Experimental Settings''', set the default scope region to <code>sco</code>, and keep <code>ioi</code> available in your scope list as well so you can pick it when you need it. For each channel, set scope to match '''where the traffic should travel'''—for example <code>#edinburgh</code> with <code>edi</code>. On '''<code>#ireland</code>''', you may use '''<code>ioi</code> or <code>sco</code>''': use <code>ioi</code> when the message should ride the Island of Ireland scoped path (IOI peering); use <code>sco</code> when you want the same channel but Scotland-wide scoped carriage on the mesh.

</div>
<span id="why-scope-matters"></span>
=== 🤷 Why scope matters ===

Without scope, repeaters have no way to know whether to carry your traffic. With it, messages travel through exactly the right part of the network.

* Keep Scottish traffic inside Scotland where appropriate.
* Allow controlled traffic to and from the Island of Ireland (IOI peering).
* Reduce unnecessary flooding.
* Keep the network easier to grow.

For example channel names and typical scopes, see [[MeshCore/Channels|Channels]]. For repeater region codes, see [[MeshCore/Regions|Regions]].

<span id="what-region-scope-means"></span>
=== 🗺️ What region scope means ===

Think of scope like a postcode on a letter — it tells the mesh where the message is meant to go.

<syntaxhighlight lang="text">sco = Scotland-wide
edi = Edinburgh area (example local)
ioi = Island of Ireland (IOI peering)</syntaxhighlight>
A message scoped to <code>sco</code> is forwarded by repeaters that carry <code>sco</code>as a region. A message scoped to <code>ioi</code> is forwarded by repeaters that carry <code>ioi</code>as a region. If scope is missing or wrong for your path, the message will go nowhere, it is dropped and ceases to exist.

<span id="wildcard-forwarding-is-not-allowed"></span>
=== 🚫 Wildcard forwarding is not allowed ===

The wildcard marker is <code>*</code>. Do not rely on it for routing — the Scottish MeshCore setup expects explicit region scopes.

In the '''Companion App''', your channel scope should always be a '''real region code''' (<code>sco</code>, <code>gla</code>, <code>ioi</code>, and so on). On '''repeaters''', CLI examples sometimes show <code>*</code> as the '''parent''' in a region tree (for example <code>region put sco *</code>); that is a different idea from wildcard '''forwarding''' and is covered in [[MeshCore/Regions|Regions]].

<span id="documented-scope-codes"></span>
=== 📋 Documented scope codes ===

{| class="wikitable"
|-
! Scope
! Typical use
|-
| <code>sco</code>
| Scotland-wide traffic
|-
| <code>cen</code>
| Central Scotland
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>gla</code>
| Glasgow area
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>sti</code>
| Stirling area
|-
| <code>per</code>
| Perth area
|-
| <code>dun</code>
| Dundee area
|-
| <code>ioi</code>
| Island of Ireland / IOI peering
|}

For most day-to-day traffic in Scotland, '''<code>sco</code>''' is the right default. Use a '''local''' code when traffic should stay in that area, regardless of channel name.

<span id="default-scope-and-per-channel-scope"></span>
=== ⚙️ Default scope and per-channel scope ===

On ScotMesh, set your '''default''' scope region to <code>sco</code>. In the mobile app this is usually under '''Experimental Settings'''. Flood packets from the companion then use <code>sco</code> unless a '''group channel''' has its own scope.

'''Per-channel scope overrides the default.''' Examples:

* <code>#glasgow</code> with <code>gla</code> keeps traffic in the Glasgow-area part of the mesh.
* '''<code>#ireland</code> with <code>ioi</code>''' — message is scoped for the Island of Ireland path (IOI peering repeaters).
* '''<code>#ireland</code> with <code>sco</code>''' — same channel name, but the packet is Scotland-wide scoped; repeaters treat it like other <code>sco</code> traffic.

Keep both <code>sco</code> and <code>ioi</code> in your available scopes so you can switch. For background, see MeshCore [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

<span id="how-to-set-region-scope-in-the-companion-app"></span>
=== 📱 How to set region scope in the Companion App ===

Menus vary by app version and platform; the usual flow is:

<syntaxhighlight lang="text">1. Open the MeshCore Companion App
2. Open the channel you want to use
3. Open the channel options or channel menu
4. Find the region scope option
5. Select or add the region code you need
6. Send with that scope active</syntaxhighlight>
Often the channel menu includes something like '''Set Region Scope''', then you pick or type the code (for example <code>sco</code>, <code>edi</code>, or <code>ioi</code>).

<span id="examples"></span>
=== 💬 Examples ===

'''Scotland-wide'''

<syntaxhighlight lang="text">Channel: #scotland
Scope: sco</syntaxhighlight>
'''Local (example)'''

<syntaxhighlight lang="text">Channel: #glasgow
Scope: gla</syntaxhighlight>
'''<code>#ireland</code> with Island of Ireland scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope: ioi</syntaxhighlight>
'''<code>#ireland</code> with Scotland-wide scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope: sco</syntaxhighlight>
The channel name does not set scope by itself — you still choose <code>ioi</code> or <code>sco</code> (or another code) in the channel settings.

<span id="quick-choices"></span>
=== ⚡ Quick choices ===

* Normal Scottish chat: default <code>sco</code>, or <code>#scotland</code> with <code>sco</code>.
* Local-only: local scope such as <code>edi</code> or <code>gla</code> when traffic should stay in that area.
* '''<code>#ireland</code>:''' <code>ioi</code> for IOI-scoped path, '''<code>sco</code>''' when you want Scotland-wide scoped carriage on that channel.
* Tests: <code>#test</code> with whichever scope you are testing (<code>tay</code>, <code>sco</code>, …).

If you are unsure, '''<code>sco</code>''' is the safe general default for Scottish-side traffic.

<span id="what-to-avoid"></span>
=== ❌ What to avoid ===

* Sending traffic with no region scope.
* Relying on wildcard forwarding.
* Assuming the channel name alone chooses routing.

<span id="summary"></span>
=== 📝 Summary ===

<syntaxhighlight lang="text">Default: sco on ScotMesh
Override per channel when needed
#ireland: ioi OR sco
Local: use the local code when traffic should stay local
Check your companion app is scoped before you send your initial messages</syntaxhighlight>
Getting scope right keeps mesh traffic logical and the mesh relaible, easier to use and simpler to grow.

MeshCore/Getting Started

2026-11-03T17:06:12Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

{{DISPLAYTITLE:Getting Started}}
<span id="getting-started-within-scotmesh"></span>
== Getting Started within ScotMesh 🏴󠁧󠁢󠁳󠁣󠁴󠁿 ==

-----

<span id="what-is-scotmesh"></span>
=== 🏴󠁧󠁢󠁳󠁣󠁴󠁿 What is ScotMesh? ===

ScotMesh is community radio messaging networks across Scotland. It uses small, low-power LoRa radios to carry short messages between people — no mobile network, no Wi-Fi, no internet required.
Think of it like a local text messaging service that works off-grid, powered by volunteer-run repeaters dotted across the country.

'''Currently both Meshtastic and Mescore networks are available'''

<span id="note-this-document-focuses-on-meschore"></span>
== '''NOTE This document focuses on Meschore''' ==

Never used MeshCore before? Good — this is the place to start. No radio knowledge needed.

<div class="sm-cx sm-cx-info">

This guide is written for '''companion node''' devices — small LoRa radios that pair with the MeshCore Companion App on your phone. More capable standalone devices do exist, but those are out of scope for this guide. If you are setting one of those up, ask in the [https://discord.gg/ytxfyuDmSt Discord] for advice.

</div>
<span id="what-you-need"></span>
=== 🎒 What you need ===

* A MeshCore '''companion node''' — a small LoRa radio that pairs with your phone over Bluetooth.
* A smartphone — Android or iPhone both work.
* That is it.

<div class="sm-cx sm-cx-info">

Not sure which companion node to get? Ask in the [https://discord.gg/ytxfyuDmSt Discord] and the community can point you in the right direction.

</div>
<span id="get-the-app"></span>
=== 📱 1. Get the app ===

Download the '''MeshCore Companion App''' on your phone.

* '''Android:''' [https://play.google.com/store/search?q=meshcore MeshCore on Google Play]
* '''iPhone:''' [https://apps.apple.com/search?term=meshcore MeshCore on the App Store]

Open the app once it has installed.

<span id="flash-the-latest-firmware-to-the-lora-device"></span>
=== 👨‍💻 2. Flash the Latest Firmware to the LoRa Device ===

Before configuring the node, flash the LoRa device with the latest correct firmware for your exact hardware.

<blockquote>'''Important:''' Do '''not''' use the firmware that came pre-installed on the node.
</blockquote>
Pre-installed firmware may be outdated, built for a different board variant, or configured incorrectly for our mesh. Using the wrong firmware can cause connection issues, missing features, failed regional settings, or unreliable repeater behaviour.

Download the latest firmware from https://meshcore.io/, making sure you select the correct build for your exact device type, for example:

* RAK4631
* Heltec
* T114
* SenseCAP
* Waveshare
* Other supported hardware

After flashing, reboot the device and confirm the firmware version before continuing with the rest of the setup.

<span id="connect-your-device"></span>
=== 🔵 3. Connect your device ===

# Make sure your LoRa device is powered on.
# In the app, tap '''Add Device''' or the connect button.
# The app will search for nearby devices over Bluetooth. Select yours from the list.
# Wait a moment for it to connect. You should see your device appear in the app.

<div class="sm-cx sm-cx-info">

If the device does not show up, make sure Bluetooth is enabled on your phone and that the device is in pairing mode. Check your device’s instructions if you are unsure.

</div>
<span id="the-companion-node-settings"></span>
=== ⚙️ 3. The companion node settings ===

<blockquote>For these settings, understanding the regional framework is important because it defines how traffic is organised and routed across the mesh. Regions (set on repeater nodes) allow the wider mesh to be split into sensible geographic areas, helping messages, adverts, and repeater traffic stay relevant to the area they are intended for while still allowing agreed neighbouring regions to interconnect where required. Setting the '''default scope''' tells the node which region it should use automatically when sending or repeating traffic that does not already have a specific scope applied. In practice, this helps keep local traffic local, reduces unnecessary flooding across unrelated areas, and improves the reliability and manageability of the mesh.
</blockquote>
Before you can send anything from your companion app, you need to set it up for use in the ScotMesh MC mesh.

<span id="connecting-a-newly-flashed-companion-node-to-scotmesh"></span>
=== Connecting a Newly Flashed Companion Node to ScotMesh ===

After flashing the latest companion-node firmware, use the '''MeshCore app''' to connect to the node by Bluetooth and configure it for ScotMesh.

<ol style="list-style-type: decimal;">
<li><p>Power on the newly flashed companion node.</p></li>
<li><p>Open the '''MeshCore app''' on your phone.</p></li>
<li><p>Make sure Bluetooth is enabled on your phone.</p></li>
<li><p>In the MeshCore app, go to the Bluetooth connection screen.</p></li>
<li><p>Scan for nearby Bluetooth MeshCore devices.</p></li>
<li><p>Select your newly flashed companion node from the list.</p></li>
<li><p>Wait for the app to connect to the node.</p></li>
<li><p>Confirm the node shows as connected in the MeshCore app.</p></li>
<li><p>Check the firmware version shown in the app and confirm it is the latest correct firmware for your device.</p></li>
<li><p>Give the node a clear and recognisable name so other ScotMesh users can identify it.</p></li>
<li><p>Open the node settings in the MeshCore app.</p></li>
<li><p>Set the LoRa/radio region to the correct UK/EU setting.</p></li>
<li><p>Open '''Experimental Settings''' and set the following:</p>
<ul>
<li>'''Default Scope:''' <code>sco</code></li>
<li>'''Default Hash Size:''' <code>3 byte</code></li></ul>
</li>
<li><p>Save or apply the settings.</p></li>
<li><p>Reboot the companion node if the app asks you to do so.</p></li>
<li><p>Reconnect to the companion node by Bluetooth after it restarts.</p></li>
<li><p>Confirm the '''Default Scope''' is still set to <code>sco</code>.</p></li>
<li><p>Confirm the '''Default Hash Size''' is still set to <code>3 byte</code>.</p></li>
<li><p>Open the ScotMesh public channel.</p></li>
<li><p>Send a short test message, for example:</p>
<p><code>Test from newly configured ScotMesh companion node</code></p></li>
<li><p>Confirm that the message sends successfully.</p></li></ol>

Once these steps are complete, the companion node should be connected to ScotMesh and ready to send messages using the Scottish default scope.

<div class="sm-cx sm-cx-warning">

The default scope is the most important setting on ScotMesh. Without it, your messages may not travel anywhere useful on our network.

</div>
<span id="send-your-first-message-in-the-scotland-channel."></span>
=== 💬 4. Send your first message in the #scotland channel. ===

# In the app, open or create a channel called <code>#scotland</code>.
# Check the channel scope is set to <code>sco</code>. If the app shows a scope option, make sure it says <code>sco</code>.
# Type a short hello and send it.

That is all you need to do. If there is a repeater nearby, your message should travel through the mesh.

<span id="nothing-coming-back"></span>
=== 🤔 5. Nothing coming back? ===

Do not worry — this is normal at first.

* '''Check your scope.''' Go back to step 2 and confirm <code>sco</code> is set as the default and on the <code>#scotland</code> channel.
* '''Check repeater coverage.''' It is best '''NOT TO USE''' [https://map.meshcore.io/ MeshCore Node Map] to see if there are any repeaters near you. It is not up to date and can give false promise of coverage. Use the discover nearby nodes Scanner in the Meshcore app tools. > The web map is inaccurate and alway out of date. The companion app map will be empty until it hears adverts. the only way to reliably check for repeaters is to use the repeater search tool in the companion app
* '''Try <code>#test</code>.''' Send a message in a channel called <code>#test</code> with scope <code>sco</code> — this is what the community uses for testing. If someone else is active they may respond.
* '''Ask for help.''' The [https://discord.gg/ytxfyuDmSt Discord] is friendly and someone will help you work out what is happening.

<span id="where-to-go-next"></span>
=== 🗺️ Where to go next ===

Once you are up and running:

* [[MeshCore/Scopes|Scopes]] explains what scope means and how to set it properly for different channels.
* [[MeshCore/Channels|Channels]] lists the agreed community channels and what scope to use with each.
* [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]] is for you if you want to set up a repeater and help the network grow.

MeshCore

2026-11-03T17:06:11Z

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

<span id="meshes"></span>
== Meshes ==

ScotMesh has both Meshtastic and MeshCore — radio messaging systems for small LoRa devices. It lets people send short messages across a volunteer-run network without needing mobile coverage, Wi-Fi, or the internet. Carry a small companion node in your pocket, connect it to your phone, and you’re on the mesh.

<span id="the-remainder-of-this-document-focuses-on-meshcore."></span>
== The remainder of this document focuses on Meshcore. ==

<span id="key-ideas"></span>
=== 💡 Key ideas ===

{| class="wikitable"
|-
! Term
! Meaning
|-
| '''Channel'''
| A named place for conversation, such as <code>#scotland</code>, <code>#glasgow</code>, or <code>#ireland</code>.
|-
| '''Scope'''
| The region code applied to messages in a channel, such as <code>sco</code>, <code>gla</code>, or <code>ioi</code>.
|-
| '''Region'''
| A code configured on a repeater to describe the area it serves.
|-
| '''Repeater'''
| A fixed node that hears MeshCore traffic and repeats it to extend coverage.
|}

<span id="new-to-scotmesh"></span>
=== 👋 New to ScotMesh? ===

* [[MeshCore/Getting Started|Getting Started]] — what it is, what you need, your first message.
* [[MeshCore/Scopes|Scopes]] — the one setting that matters most.
* [[MeshCore/Channels|Channels]] — where to talk and what scope to use.
* [[MeshCore/FAQ|FAQ]] — quick answers to common questions.

<span id="setting-up-a-repeater"></span>
=== 📡 Setting up a repeater? ===

* [[MeshCore/Repeater Quick Setup|Repeater Quick Setup]] — start here for hardware and commands.
* [[MeshCore/Regions|Regions]] — full region code reference and configuration policy.
* [[MeshCore/Observers|Observers]] — MQTT map uplink setup.

<span id="interested-in-the-technical-detail"></span>
=== 🔧 Interested in the technical detail? ===

* [https://blog.meshcore.io/2026/01/20/region-filtering Region Filtering]
* [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region]
* [https://docs.meshcore.io/cli_commands/ CLI Commands]

-----

<div class="sm-cx sm-cx-warning">

'''ScotMesh network policy:''' wildcard <code>*</code> forwarding is not allowed. Companion App users should set their default region scope to <code>sco</code> under '''Experimental Settings'''. Repeater owners should use <code>region denyf *</code>. See [[MeshCore/Regions|Regions]] for detail.

</div>

File:Scotmesh-tx-delay-route.jpg

2026-11-03T17:06:11Z

Admin: == Summary == Importing file

== Summary ==
Importing file

Main Page

2026-11-03T16:54:21Z

Admin: Restyle landing to match scotmesh.net (hero + net-cards)

__NOTOC__ __NOEDITSECTION__
<div class="sm-hero">
<div class="sm-rule">ScotMesh Wiki</div>
<div class="sm-h1">Two meshes across Scotland, one wiki.</div>
<p class="sm-lead">Guides, setup and reference for both ScotMesh radio networks — MeshCore and Meshtastic. Pick a network to get started.</p>
<div class="sm-btns"><span class="b-primary">[https://discord.gg/ytxfyuDmSt Join the community]</span> <span>[https://scotmesh.uk Forum]</span></div>
</div>

<div class="sm-grid">
<div class="net-card meshcore">
<div class="net-head">[[File:ScotMesh-meshcore-mark.svg|link=MeshCore|38px|alt=MeshCore]]<span class="net-meta"><span class="net-name">MeshCore</span><span class="net-for">Held Up by Repeaters</span></span></div>
<p>Long-range LoRa on cheap radios, carried by fixed repeaters on high ground. Getting started, regions, scopes, channels, repeater setup and the FAQ.</p>
<div class="net-go">[[MeshCore|Open the MeshCore guides →]]</div>
</div>
<div class="net-card meshtastic">
<div class="net-head">[[File:ScotMesh-meshtastic-mark.svg|link=Meshtastic|38px|alt=Meshtastic]]<span class="net-meta"><span class="net-name">Meshtastic</span><span class="net-for">Scotland's Original Mesh</span></span></div>
<p>Long-range LoRa messaging with an app on your phone, where every radio can repeat what it hears. Introduction and setup guides.</p>
<div class="net-go">[[Meshtastic|Open the Meshtastic guides →]]</div>
</div>
</div>

<span class="sm-join-note">Forum invite code <code>VVAGXJN7BQ</code></span>

File:ScotMesh-meshcore-mark.svg

2026-11-03T16:54:20Z

Admin: == Summary == Importing file

== Summary ==
Importing file

File:ScotMesh-meshtastic-mark.svg

2026-11-03T16:54:20Z

Admin: == Summary == Importing file

== Summary ==
Importing file

Main Page

2026-11-03T16:49:52Z

Admin: Remove retired GitHub contribute link

__NOTOC__ __NOEDITSECTION__
<div class="sm-hero">
[[File:ScotMesh-lockup.svg|link=|alt=ScotMesh|class=sm-hero-logo|300px]]
<div class="sm-tagline">Off-grid radio mesh across Scotland</div>
</div>

Welcome to the '''ScotMesh Wiki''' — community documentation for the ScotMesh networks. Pick a network to get started.

<div class="sm-grid">
<div class="sm-card meshcore">
[[File:ScotMesh-meshcore-lockup.svg|link=MeshCore|alt=scotmesh/meshcore|class=sm-cardlogo|180px]]
<p>Getting started, regions, channels, scopes, repeaters and the FAQ.</p>
<span class="sm-go">[[MeshCore|Browse MeshCore →]]</span>
</div>
<div class="sm-card meshtastic">
[[File:ScotMesh-meshtastic-lockup.svg|link=Meshtastic|alt=scotmesh/meshtastic|class=sm-cardlogo|180px]]
<p>Introduction and guides for ScotMesh on Meshtastic.</p>
<span class="sm-go">[[Meshtastic|Browse Meshtastic →]]</span>
</div>
</div>

== Join the community ==
Get involved, ask questions, and help the network grow.

<div class="sm-join">
<span class="j-discord">[https://discord.gg/ytxfyuDmSt Join the Discord]</span>
<span class="j-forum">[https://scotmesh.uk Join the Forum]</span>
</div>
<span class="sm-join-note">Forum invite code <code>VVAGXJN7BQ</code></span>

Main Page

2026-11-03T16:44:55Z

Admin: Front page: Join the community (Discord + Forum code)

MediaWiki:Common.css

2026-11-03T16:44:54Z

Admin: Front page: styled Discord + Forum join

MediaWiki:Common.css

2026-11-03T16:42:14Z

Admin: Brand callouts (Wiki.js -> ScotMesh) + content styles

Main Page

2026-11-03T16:24:54Z

Admin: Homepage: ScotMesh lockup hero + network lockup cards

__NOTOC__ __NOEDITSECTION__
<div class="sm-hero">
[[File:ScotMesh-lockup.svg|link=|alt=ScotMesh|class=sm-hero-logo|300px]]
<div class="sm-tagline">Off-grid radio mesh across Scotland</div>
</div>

Welcome to the '''ScotMesh Wiki''' — community documentation for the ScotMesh networks. Pick a network to get started.

<div class="sm-grid">
<div class="sm-card meshcore">
[[File:ScotMesh-meshcore-lockup.svg|link=MeshCore|alt=scotmesh/meshcore|class=sm-cardlogo|180px]]
<p>Getting started, regions, channels, scopes, repeaters and the FAQ.</p>
<span class="sm-go">[[MeshCore|Browse MeshCore →]]</span>
</div>
<div class="sm-card meshtastic">
[[File:ScotMesh-meshtastic-lockup.svg|link=Meshtastic|alt=scotmesh/meshtastic|class=sm-cardlogo|180px]]
<p>Introduction and guides for ScotMesh on Meshtastic.</p>
<span class="sm-go">[[Meshtastic|Browse Meshtastic →]]</span>
</div>
</div>

----
''Contribute on GitHub: [https://github.com/ScotMesh/scotmesh-wiki ScotMesh/scotmesh-wiki]''

MediaWiki:Sidebar

2026-11-03T16:24:53Z

Admin: Network menus: ScotMesh MeshCore / Meshtastic

* navigation
** mainpage|Home
* ScotMesh MeshCore
** MeshCore|Introduction
* ScotMesh Meshtastic
** Meshtastic|Introduction
* SEARCH
* TOOLBOX

File:ScotMesh-meshcore-lockup.svg

2026-11-03T16:24:53Z

Admin: == Summary == Importing file

== Summary ==
Importing file

File:ScotMesh-lockup.svg

2026-11-03T16:24:52Z

Admin: == Summary == Importing file

== Summary ==
Importing file

File:ScotMesh-meshtastic-lockup.svg

2026-11-03T16:24:52Z

Admin: == Summary == Importing file

== Summary ==
Importing file

MediaWiki:Citizen-footer-tagline

2026-11-03T16:18:42Z

Admin: ScotMesh footer tagline

Off-grid radio mesh across Scotland

MediaWiki:Citizen-footer-desc

2026-11-03T16:18:41Z

Admin: ScotMesh footer description

Community documentation for the ScotMesh mesh networks — MeshCore and Meshtastic.

Main Page

2026-11-03T16:17:28Z

Admin: Suppress TOC/section-edit on landing

__NOTOC__ __NOEDITSECTION__
<div class="sm-tagline">Off-grid radio mesh across Scotland</div>

Welcome to the '''ScotMesh Wiki''' — community documentation for the ScotMesh networks. Pick a network to get started.

<div class="sm-grid">
<div class="sm-card meshcore">
<h2>[[MeshCore]]</h2>
<p>Getting started, regions, channels, scopes, repeaters and the FAQ.</p>
</div>
<div class="sm-card meshtastic">
<h2>[[Meshtastic]]</h2>
<p>Introduction and guides for ScotMesh on Meshtastic.</p>
</div>
</div>

----
''Contribute on GitHub: [https://github.com/ScotMesh/scotmesh-wiki ScotMesh/scotmesh-wiki]''

Meshtastic

2026-11-03T15:55:37Z

Admin: Meshtastic section stub

{{DISPLAYTITLE:Meshtastic}}
'''ScotMesh Meshtastic''' — documentation for the ScotMesh Meshtastic network.

<div class="sm-tagline">Section layout · content migration in progress</div>

Introduction and setup guides coming over from the old wiki.