From f12b074337ec23272bd03c561923e7a08afe29f3 Mon Sep 17 00:00:00 2001 From: pdxlocations Date: Thu, 28 Sep 2023 21:40:08 -0700 Subject: [PATCH] trunk-ignore --- docs/about/faq.mdx | 2 ++ docs/configuration/radio/channels.mdx | 4 ++-- docs/configuration/remote-admin.mdx | 2 +- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/about/faq.mdx b/docs/about/faq.mdx index 33e29282..ba1e9775 100644 --- a/docs/about/faq.mdx +++ b/docs/about/faq.mdx @@ -51,6 +51,7 @@ The Meshtastic App on Apple Clients require the following minimum OS versions: i See [Apple Apps](/docs/software/apple/installation) + ### After a fresh firmware install, my node is not connecting via Bluetooth. What should I do? Try forgetting the Bluetooth connection from the iOS/iPadOS/macOS System Settings. Re-pair and try again. This is a security measure and there is no workaround for it. It prevents apps and other accessories from spoofing an existing accessory by un-pairing and "re-pairing" themselves without the users' knowledge. @@ -111,6 +112,7 @@ Updating firmware varies with hardware. See [Flashing Firmware](/docs/getting-st The LoRa radio on the node is still active and will wake up the CPU when the device is sleeping. If your phone is in range, the node will relay any messages your phone may have missed. If you're in range and your device is active, messages have not been lost. + ### My device has gone to sleep and I can't send any messages. Once the node wakes up from sleep, your phone will relay any delayed messages through your node and to the mesh network. Give it a few minutes and it'll do the right thing. diff --git a/docs/configuration/radio/channels.mdx b/docs/configuration/radio/channels.mdx index 63ca1244..ab0e2f05 100644 --- a/docs/configuration/radio/channels.mdx +++ b/docs/configuration/radio/channels.mdx @@ -153,7 +153,7 @@ meshtastic --ch-set name "My Channel" --ch-set psk random --ch-set uplink_enable ::: - + ### Name ```shell title="Set channel name for the PRIMARY channel" @@ -162,7 +162,7 @@ meshtastic --ch-set name MyChannel --ch-index 0 # with spaces meshtastic --ch-set name "My Channel" --ch-index 0 ``` - + ### PSK If you use Meshtastic for exchanging messages you don't want other people to see, `random` is the setting you should use. Selecting `default` or any of the `simple` values from the following table will use publicly known encryption keys. They're shipped with Meshtastic source code and thus, anyone can listen to messages encrypted by them. They're great for testing and public channels. diff --git a/docs/configuration/remote-admin.mdx b/docs/configuration/remote-admin.mdx index a4960851..cf1422fb 100644 --- a/docs/configuration/remote-admin.mdx +++ b/docs/configuration/remote-admin.mdx @@ -76,7 +76,7 @@ For this step you need physical access to both the nodes. ```shell meshtastic --seturl the-url-from-step-2 ``` - + 5. Run `meshtastic --info` and confirm that the "Complete URL" is the same for both of the nodes. At this point you can take your remote node and install it far away. You will still be able to change any of its settings.