YYC Mesh Radio Settings

Come test the new YYC Mesh radio settings and participate in a fresh Meshtastic network!

Before joining, please read the community guidelines below.

Scan the QR code or click below to join directly:

NOTE: You may receive an error that the radio settings failed to save channel configuration. This just means the node rebooted with the new settings before it could update the Primary channel. If your Primary channel shows a red lock, simply go to Settings → Channels → Primary Channel → Save.

ALSO NOTE: If you have private and/or encrypted secondary channels setup, you may need to rename the public channel to “Custom”.

If you prefer to enter the settings manually, the radio settings are recorded below.

NOTE: iOS currently has a bug when applying custom radio settings, so use one of the following:

Android
Meshtastic Web
Meshtastic CLI

Custom LongModTurbo Settings

Navigate to Meshtastic App → Settings → LoRa and configure:

Use Preset = OFF
Bandwidth = 500
Spread Factor = 11
Coding Rate = 8
Frequency Override = 902.6875 MHz

The public channel is using the default Primary Channel 0 settings (Key: AQ==).

Community Guidelines

Since this is a public test rollout, please adhere to some guidelines to make the shared experience positive for everyone. These are subject to change as testing progresses:

Ensure you are running the latest stable Meshtastic firmware (currently 2.6.11). Running newer Alpha builds is acceptable and encouraged.
Refrain from any MQTT uplink/downlink activity (use LongFast instead). Personal ZERO-hop usage with the official Meshtastic MQTT servers is acceptable.
Do not use Router or Repeater roles on the public mesh. Use Client, Client_Base, or Client_Mute. (Client and Client_Base still route and repeat and allow you to contribute.)
Some nodes may need more hops depending on location. Test with 3 hops first and increase only if necessary. For unattended stationary nodes, limit them to 3 hops or fewer.
If setting up strategic repeating nodes (Client or Client_Base), ensure they can be reached for firmware upgrades or remote admin if needed. This avoids “abandoned rogue node” issues.
For position (GPS) and telemetry updates on stationary nodes, limit update intervals to 1 hour or more. For tracking/vehicle nodes, use Smart Position updates.
We are temporarily limiting BBS-style auto-responding nodes during testing. Contact [email protected] on the official Meshtastic Discord if you’d like to participate.

Currently, F0X0 (F0X) has been set up for BBS mesh activities. Please thank him for his work on getting it optimally configured, placed, and tested.

In general, the rule is simple — be respectful of your fellow mesh enthusiasts.

Most importantly: Have fun and check in to say hi!