From 9e2c9ff0abc937ef1e1d71bc3a19d91a75f37ae0 Mon Sep 17 00:00:00 2001 From: James Guillochon Date: Thu, 4 Jan 2024 08:06:38 -0800 Subject: [PATCH 1/2] Clarify step 4 a bit in the private primary/default secondary tip I think users would reasonably assume that the LoRa channel is by default set to their region's channel and are unaware of the hashing algo used to generate the channel number. I think rewriting this way makes it less likely for users to make this mistake. --- docs/configuration/tips.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuration/tips.mdx b/docs/configuration/tips.mdx index 48c1d2bb..3e0e113d 100644 --- a/docs/configuration/tips.mdx +++ b/docs/configuration/tips.mdx @@ -29,7 +29,7 @@ If you'd like to connect with other Meshtastic users but only share your locatio 1. Ensure you have not changed the LoRa [Modem Preset](/docs/configuration/radio/lora#modem-preset) from the default `unset` / `LONG_FAST`. 2. On your PRIMARY channel, set anything you'd like for the channel's name and choose a random PSK. 3. Enable a SECONDARY channel named "LongFast" with PSK "AQ==". -4. Since the radio's frequency is automatically changed based on your PRIMARY channel's name, you will have to manually set it back to your region's default (in LoRa settings) in order to interface with users on the default channel: +4. If your LoRa channel is set to the default (`0`), the radio's frequency will be automatically changed based on your PRIMARY channel's name. In this case, you will have to manually set it back to your region's default (in LoRa settings) in order to interface with users on the default channel: ### Default Primary Channels by Region @@ -65,4 +65,4 @@ This configures the frequency the radio is set to. Check out the [frequency cal - If you are part of a large mesh and don't know what a setting does, don't change it (unless you're super curious). - Leave your [MAX HOPS](/docs/configuration/radio/lora#max-hops) set to 3 unless you're sure you need more (or less) to reach your destination node. - TEST your settings and hardware before you install in hard-to-reach locations. -- Connecting a node to the [public MQTT server](http://localhost:3000/docs/configuration/module/mqtt#connect-to-the-default-public-server) may publish the locations of all nodes in your mesh to the internet. This will also add every globally connected node to your node database and potentially flood your mesh with all types of packets. \ No newline at end of file +- Connecting a node to the [public MQTT server](http://localhost:3000/docs/configuration/module/mqtt#connect-to-the-default-public-server) may publish the locations of all nodes in your mesh to the internet. This will also add every globally connected node to your node database and potentially flood your mesh with all types of packets. From 0ef6c449ff6f928c91a3c5517ac056cfb8f350d9 Mon Sep 17 00:00:00 2001 From: James Guillochon Date: Thu, 4 Jan 2024 08:28:36 -0800 Subject: [PATCH 2/2] Newline removed GitHub's web editor automatically added the newline, annoying