From 7dbe07eb39f4c8a177126fdb531b722022c42e93 Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Wed, 28 Feb 2024 20:29:40 +0100 Subject: [PATCH] Clarify broadcast interval for Device Metrics and NodeInfo --- docs/configuration/module/telemetry.mdx | 4 +++- docs/configuration/radio/device.mdx | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/configuration/module/telemetry.mdx b/docs/configuration/module/telemetry.mdx index d6b4bd5a..bb3ada3f 100644 --- a/docs/configuration/module/telemetry.mdx +++ b/docs/configuration/module/telemetry.mdx @@ -44,7 +44,9 @@ Default is `900` seconds (15 minutes). 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 diff --git a/docs/configuration/radio/device.mdx b/docs/configuration/radio/device.mdx index a2794b6a..5ba782b0 100644 --- a/docs/configuration/radio/device.mdx +++ b/docs/configuration/radio/device.mdx @@ -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 -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