The mesh is growing, and with it, so are the number of repeaters, companions and other parts of the mesh.
In order to help the mesh grow, there are a few changes to make to help the mesh grow further.
This information was last updated on May 10, 2026.
The way MeshCore devices communicate is through a "path hash", which historically was a one-byte ID for each repeater or companion. So, one device might have an ID of be. There are 256 different IDs, and this is fine until there are lots of devices on the mesh, and especially until our mesh starts to connect with other parts of Australia, where suddenly there are other devices called be.
You can see this as an issue on the Eastmesh map, where that is getting confused about where some messages are actually going - since some devices share the same codes across other states.
As of May 2026, our recommendation is to set repeaters to support 2-byte path hashes. So, instead of having 256 different possible IDs like be, you now have 65,536 possible IDs, like be0a.
Here's more on the Meshcore.io wiki.
First, your repeater should be running v1.14 or higher of the firmware. We'd recommend the latest builds.
To change multi-byte settings, you'll need Command Line access to your repeater (typically through the MeshCore app's repeater admin tool), and send this command:
set path.hash.mode 1
and then reboot, remembering to sync your clock afterwards if you need to.
Our mesh is currently not interacting with meshes in NSW or the NT; and is not big enough, yet, to require region codes.
For companions, the devices that are sending the message (not just repeating them), we recommend leaving your companions on 1-byte hashes for now.
This is the recommendation of the Meshcore wiki, and means you shouldn't be affected by older repeaters still on old firmware.
As repeaters move over to newer firmware versions, companions will be recommended to move. Keep your eyes on the #public channel, or this wiki.
Our mesh is currently not interacting with meshes in NSW or the NT; and is not big enough, yet, to require region codes.