Companion Settings
Two settings to check before using your companion radio on Thumb Mesh: two-byte paths and the Michigan region.
| Setting | Thumb Mesh value | Purpose |
|---|---|---|
| Default path hash size | 2 bytes | Uses two bytes to identify each repeater in a path, reducing ambiguity between repeaters with the same one-byte prefix. |
| Default region scope | mi | Scopes outgoing flood traffic to the Michigan region as configured on the repeaters. |
Enter mi in lowercase, without quotation marks or a leading #. This is a mesh routing scope, not the country or frequency preset.
Use current compatible firmware and apps. Standard MeshCore companion firmware needs version 1.15 or later for the default region setting; repeaters must support version 1.14 or later to forward two-byte paths.
MeshCore app
- Connect to your companion radio and open Settings using the gear icon.
- Find Default Path Hash Size and choose 2-byte. In newer app versions this is on the main settings screen, under the network settings; older versions place it under Experimental Settings.
- Open Default Region Scope in the same settings area. Add
miif it is not listed, then select it as the default. Adding a region to the list alone does not select it. - Confirm or save the change when prompted, then reopen the settings to check that the path size is two bytes and the default region is
mi.
For existing channels, check Set Region Scope in the channel's menu. Use the default region or select mi; a channel-specific choice can override the default.
MeshCore Open
- Connect to the radio. Open Settings → Radio Settings.
- Set Node ID size in paths to 2 bytes, then tap Save. This control sets the path hash size.
- Return to Settings → Regions. Choose Add region and enter
miif it is not already listed. - Set Radio default region to
mi. Wait for the confirmation that the radio default was updated. - Set Default region to Radio default (mi), or explicitly to
mi. Check existing channels for any region override.
Both region controls matter. “Default region” supplies a default for channel messages in this app. “Radio default region” stores the default on the companion itself, so it also applies to other outgoing floods and other connected apps. If the radio control is missing, check your firmware and app versions.
WADAMESH
Make these changes on the radio's screen. The current interface groups them under Settings → Radio & Mesh; older builds may arrange the controls differently.
- Open Settings → Radio & Mesh and find the routing controls.
- Set Multi-byte routing (path hash) to 2 bytes.
- In Region scope (#tag, blank = none), enter
mi. WADAMESH accepts the name without the#, despite the field's label. Leave the text field to apply the change. - Enable Scope direct msgs to region so direct-message, login and administration floods also use
mi. This makes the scope apply beyond channel messages; attempts to find a destination through repeaters outside the permitted region may no longer get through. - Return to the settings and confirm both values. In Chats, hold an existing channel and check its region/scope settings for an override.
Choose the radio preset before making these changes, and recheck them if you change presets later.
mishmesh
The path size can be changed on the radio. In the implementation checked for this guide, the global default region is set through a connected companion app.
- On the radio, open the app menu, then Settings → Experimental → Path hash size. Select 2 byte.
- Return to the home screen and press Down to open the quick toggles. Enable Bluetooth; its tile shows the pairing PIN.
- Connect with the MeshCore app and follow the MeshCore instructions above to set Default Region Scope to
mi. Alternatively, use MeshCore Open and set Radio default region tomi. - Read the setting back in the connected app before disconnecting. The default is saved on the radio and remains available when using mishmesh without the phone.
A chat's Region option is a per-chat override, not the global default. Leave that override empty to inherit the radio default, or set it to mi. Changing only one chat does not configure the radio's default scope.
Do companions need the region hierarchy?
No. Repeater operators configure the forwarding hierarchy: which regions exist, their parent–child relationships, and which scoped floods the repeater will forward. A companion selects a region name such as mi; it does not need a copy of that hierarchy. Adding mi to an app's region list does not create or change any repeater configuration.
The scope controls outgoing flood traffic. It is not an incoming-message filter, and it does not prevent your companion from receiving traffic sent under other scopes. Direct traffic using an already-known route is distinct from flood routing.
Check your setup
Reconnect and verify 2 bytes and mi, then send a short message in #test. Check that existing channels inherit mi or explicitly use it. A default-path change does not necessarily rewrite paths already learned for individual contacts.
If you can hear messages but yours are not getting through, confirm that nearby repeaters allow mi and support two-byte paths. Selecting a scope on your companion cannot make an unconfigured repeater forward it.
Instructions checked 7 November 2026. Menu labels can vary by release. References: MeshCore default scope, region filtering, path hash sizes, MeshCore app release notes, MeshCore Open source, WADAMESH guide, WADAMESH source, and mishmesh source.