mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-02-21 03:25:51 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #1057 from GUVWAF/broadcastInterval

Browse source 
Clarify broadcast interval for Device Metrics and automatic NodeInfo
This commit is contained in:
Ben Meadors 2024-02-28 18:12:58 -06:00 committed by GitHub
parent 282b6f2e4c 7dbe07eb39
commit 540dc93170
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/configuration/module/telemetry.mdx
View file

@ -46,6 +46,8 @@ How often we should send Device Metrics over the mesh.
Default is `900` seconds (15 minutes). Default is `900` seconds (15 minutes).
Device Metrics to a connected client app will always be sent once per minute, regardless of this setting.
### Environment Screen Enabled ### Environment Screen Enabled
Show the environment telemetry data on the device display. Show the environment telemetry data on the device display.

2
docs/configuration/radio/device.mdx
View file

@ -78,7 +78,7 @@ This is the GPIO pin number that will be used for the PWM buzzer, if your device
### Node Info Broadcast Seconds ### Node Info Broadcast Seconds
This is the number of seconds between NodeInfo message broadcasts from the device. The device will still respond ad-hoc to NodeInfo messages when a response is wanted. This is the number of seconds between NodeInfo message (containing i.a. long and short name) broadcasts from the device. The device will still respond ad-hoc to NodeInfo messages when a response is wanted. When the device hears any packet from a node it doesn't know yet, it will send its NodeInfo and ask for a response automatically.
### Double Tap as Button Press ### Double Tap as Button Press