The recommended settings for MESH-Roslagen are based off the settings from STHLM-MESH, as they are our closest large mesh. By having compatible settings, both meshes can function as one, as long as their are nodes that bridge the gap. As such, we use EU_868 and MEDIUM_FAST in MESH-Roslagen as well. Though as we are not as tight a mesh as down town, some settings are slightly more aggressive.
The ambition for MESH-Roslagen is to maintain a “true” mesh - i.e. without bridging by MQTT over the Internet. However MQTT is used - without being part of the mesh traffic - to collect stats about nodes and to create map information.
LoRa configuration
| Name |
Value |
Notes |
| Region |
EU_868 |
868 MHz-bandet is the common in Europe, and used by near-by meshes |
| Modem Preset |
MEDIUM_FAST |
Sets how the selected band is used - the default LONG_FAST can cover longer ranges, but does not handle many nodes as well |
| Ignore MQTT |
True |
Your node will not relay MQTT messages to the mesh |
| OK to MQTT |
True |
(Optional) Approve sharing your traffic to MQTT servers, useful for mapping services (Note: this is a plea to other nodes - there is no technical limitation attached to this setting.) |
| Transmit enabled |
True |
Makes your node actually transmit on the selected band and preset |
| Override duty cycle |
False |
Makes sure the node respects laws that relate to the 868 MHz band |
| Number of Hops |
3 eller 4 |
Number of nodes allowed to hop to deliver a message - a too large value can be damaging to the mesh since it causes excess traffic. |
Channel configuration
| Name |
Value |
Notes |
| Index |
0 |
The primary channel - that is the channel used by modules, and which sets the Frequency slot for the LoRa radio |
| Channel name |
MediumFast |
This is the open, default channel where you can message all other nodes |
| PSK |
AQ== |
A globally shared PSK, i.e. there is (effectively) no encryption on this channel. |
| Uplink enabled |
False |
Used for MQTT-nodes |
| Downlink enabled |
False |
Used for MQTT-nodes |
| Position enabled |
True |
(Optional) Allows your node to periodically share position data to the mesh |
| Precise location |
True |
(Optional) Choose False to send a less precise location |
Any other channels are up to you!
User configuration
| Name |
Value |
Notes |
| Long name |
Your choice |
By default this is Meshtastic <hex value> - set this to something nice so others know who they are talking to! Should be unique per node. |
| Short name |
Your choice |
4 characters that indicate a specific node. Many choose “their” prefix, and an incremental number, like baz1, baz2, etc. Should be unique per node. |
| Licensed amateur radio |
False |
Even if you are a licensed HAM operator, you should leave this as False, as it disables encryption and leaves your node incompatible with the rest of the mesh. |
| Unmessageable |
False |
Marks your node as unable to receive messages - useful for infrastructure nodes. |
Device configuration
| Name |
Value |
Notes |
| Device role |
CLIENT eller CLIENT_MUTE |
Basically always use one of these roles. Avoid ROUTER and REPEATER rolls. Read more at STHLM-MESH. |
| Rebroadcast mode |
ALL |
Makes your node relay all messages |
| Node Info broadcast interval |
2 hours (7200 seconds) |
How often your node should announce itself to the mesh |
| Time Zone |
CET-1CEST,M3.5.0,M10.5.0/3 |
For accurate time display in logs and on device |
Position configuration (Optional)
| Name |
Value |
Notes |
| Broadcast interval |
2 hours (7200 seconds) |
How often your node will share it’s position to the mesh |
| Smart position |
True |
Set your node to transmit a position more often, if you are moving around |
