MeshCore Defaults
MeshCore — Edmonton defaults
MeshCore is the primary mesh stack in YEG. Project home: meshcore.io · Docs: docs.meshcore.io · Source: github.com/meshcore-dev/meshcore · Discord: meshcore.gg · Map: map.meshcore.io
YEG MeshCore radio settings
Match these exactly to be heard on the local mesh. Confirm in Discord before changing — settings can shift as the network evolves.
| Setting | Value |
|---|---|
| Frequency | 910.525 MHz |
| Bandwidth | 62.5 kHz |
| Spreading factor | SF7 |
| Coding rate | 4/5 |
| TX power | 22 dBm |
Region & legality
| Setting | Value |
|---|---|
| Region | North America (902–928 MHz ISM band) |
| Maximum EIRP | 30 dBm (1 W) per Industry Canada RSS-210 |
EIRP = transmitter power + antenna gain − feedline loss. 22 dBm at the radio + a 5 dBi antenna ≈ 27 dBm EIRP, comfortably under 30. See /p/regulatory for details.
Node modes
| Mode | Description | Power |
|---|---|---|
| Companion | Handheld, paired with the phone app over BLE | Battery / USB |
| Repeater | Store-and-forward — helps other traffic propagate | Mains / solar / fixed |
| Room Server | Hosts a persistent named "room" (chat channel) others can join | Mains / solar / fixed |
| Sensor | Reports telemetry only | Either |
| Terminal Chat | Standalone chat node with screen + buttons, no phone needed | Either |
Run Companion unless you're deliberately deploying infrastructure.
Public channel
MeshCore ships with a public well-known channel for discovery. Common convention: stay on it for first contact, then move to a named room or private channel for ongoing chat.
Local rooms
⚠ Admin: fill these in. The Edmonton mesh may host one or more named rooms on dedicated room-server nodes. Room URLs / keys are shared in the YEG MeshCore Discord — list the active ones here once you have them.
Pairing the Companion app
Companion nodes pair with the official MeshCore mobile app over BLE. After pairing:
- Set your display name.
- Confirm radio settings match the YEG defaults above.
- Join
Publicand any local rooms you've been invited to. - Send a test message and watch for replies — discovery on a small mesh can take time.
There is also meshcore.liamcottle.net — a web-based MeshCore client that pairs over Web Bluetooth in Chromium browsers.
Hardware
MeshCore runs on most LoRa boards Meshtastic supports — Heltec V3, LILYGO T-Beam, RAK Wisblock 4631, the Seeed SenseCAP T1000, RAK's tag-format trackers, and others. See hardware tiers for a curated list, and confirm board support against the current YEG-recommended firmware before flashing.
Differences from Meshtastic
| MeshCore | Meshtastic | |
|---|---|---|
| Routing | Source-routed with discovery | Flood, hop-limited |
| Channels | Rooms (server-hosted) + private channels | 8 PSK slots |
| Default airtime | Designed to be lower | Higher |
| Maturity | Smaller but actively developed | Larger ecosystem |
| YEG community | Primary | Secondary |
The two stacks share the band but not the protocol — a MeshCore node and a Meshtastic node will not hear each other's messages.