Merge pull request #523 from GUVWAF/master

Clarifications about check/cross mark and retransmissions
This commit is contained in:
Thomas Göttgens 2022-11-26 10:40:54 +01:00 committed by GitHub
commit 018ebf5e51
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions

View file

@ -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?

View file

@ -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.