From 44267b44bb28cbcd901cbd89ab877ba7f51c534c Mon Sep 17 00:00:00 2001 From: Daniel Schlapa Date: Fri, 25 Nov 2022 13:06:02 +0100 Subject: [PATCH 1/4] Update faq.mdx Link to the Functionality of the T-Beam Buttons added --- docs/about/faq.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/about/faq.mdx b/docs/about/faq.mdx index 00530cdf..cf861f1b 100644 --- a/docs/about/faq.mdx +++ b/docs/about/faq.mdx @@ -96,6 +96,10 @@ Hold down the left PWR button for about 10 seconds and the display should turn o Push the left PWR button for about 1 second. +### Functionality of the T-Beam Buttons ### + +[T-Beam Buttons](/docs/hardware/devices/tbeam/buttons) explain here + ### Where do I purchase the device hardware? Each [supported device](/docs/hardware/devices/tbeam) has a "Purchase Link". From 31f8522f18390d55ed4981707e49b470376aca15 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=B6ttgens?= Date: Fri, 25 Nov 2022 13:25:08 +0100 Subject: [PATCH 2/4] Update faq.mdx --- docs/about/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/about/faq.mdx b/docs/about/faq.mdx index cf861f1b..55535e93 100644 --- a/docs/about/faq.mdx +++ b/docs/about/faq.mdx @@ -98,7 +98,7 @@ Push the left PWR button for about 1 second. ### Functionality of the T-Beam Buttons ### -[T-Beam Buttons](/docs/hardware/devices/tbeam/buttons) explain here +[T-Beam Buttons](/docs/hardware/devices/tbeam/buttons) explained here ### Where do I purchase the device hardware? From 5ac29626a16bd293d243720db3a5be1e252df162 Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Sat, 26 Nov 2022 09:40:45 +0100 Subject: [PATCH 3/4] Clarify check and cross mark meaning --- docs/about/faq.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/about/faq.mdx b/docs/about/faq.mdx index 55535e93..ec633739 100644 --- a/docs/about/faq.mdx +++ b/docs/about/faq.mdx @@ -27,8 +27,8 @@ Minimum requirement is Android 5 (Lollipop 2014, first BLE support), however And - Empty Cloud - Queued on the app to be sent to your device. - Up Arrow - Queued on the device to be sent over the mesh. -- Check Mark - Delivered over the mesh. -- Cross Mark - Error. +- Check Mark - At least one other device on the mesh confirmed it received the message. +- Cross Mark - No confirmation was received after the default three retransmissions. ### How can I clear the message history? From f2d3652f68e6325f3fb772c15049eefd3df7bc49 Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Sat, 26 Nov 2022 09:42:25 +0100 Subject: [PATCH 4/4] Clarification about retransmissions --- docs/about/overview/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/about/overview/index.mdx b/docs/about/overview/index.mdx index f72799eb..b69ddf3f 100644 --- a/docs/about/overview/index.mdx +++ b/docs/about/overview/index.mdx @@ -7,8 +7,8 @@ sidebar_position: 2 ## How it works -When you send a message on your Meshtastic companion app, it is relayed to the radio using Bluetooth. That message is then broadcast by the radio three times over a certain interval in order to create redundancy for lost packets. +When you send a message on your Meshtastic companion app, it is relayed to the radio using Bluetooth. That message is then broadcasted by the radio. If it hasn't received a confirmation from any other device after a certain timeout, it will retransmit the message up to three times. -When a receiving radio captures a packet, it checks to see if it has heard that message before. If it has it ignores the message. If it hasn't heard the message, it will rebroadcast it at a certain interval three times. +When a receiving radio captures a packet, it checks to see if it has heard that message before. If it has it ignores the message. If it hasn't heard the message, it will rebroadcast it. For each message a radio rebroadcasts, it marks the "hop limit" down by one. When a radio receives a packet with a hop limit of zero, it will not rebroadcast the message. \ No newline at end of file