Coerce minimum telemetry interval of 30 minutes on defaults and make new default interval one hour #5086
Conversation
…new default interval one hour
thebentern
requested review from
caveman99,
jp-bennett,
GUVWAF,
garthvh and
andrekir
|
something to consider in the future is coalescing the Telemetry oneOfs into a single broadcast. the 16 byte header makes splitting up in separate small packets very inneficient. |
There was a problem hiding this comment.
LGTM, but maybe after this we should consider changing the "online" status of nodes in the Android/iOS app from 15 min. to 2 hours, which is what the firmware uses. DeviceTelemetry might be the only packet that keeps a node "online", so it means they will switch between online and offline all the time now.
|
good point! both Android and iOS are using 2 hours for online nodes, so we're all set there. |
|
@andrekir Ah, looks like iOS is indeed using two hours already, but Android still uses 15min., right? https://github.com/meshtastic/Meshtastic-Android/blob/700d8d3460eff858c216c4eef5e9d254fcfd5811/app/src/main/java/com/geeksville/mesh/NodeInfo.kt#L189 |
|
@GUVWAF |
* Coerce minimum telemetry interval of 30 minutes on defaults and make new default interval one hour (meshtastic#5086) * Coerce minimum telemetry interval of 30 minutes on defaults and make new default interval one hour * Smaller log messages * Add buzzer feedback on GPS toggle (meshtastic#5090) Triple Press on buttons toggles GPS enable/disable. This enhancement plays a triple-beep so that users of devices with buzzers can get audible feedback about whether they have turned the GPS off or on. This is especially valuable for screenless devices such as the T1000E where it may not be immediately obvious the GPS has been disabled. --------- Co-authored-by: Ben Meadors <[email protected]> Co-authored-by: Technologyman00 <[email protected]>
* Coerce minimum telemetry interval of 30 minutes on defaults and make new default interval one hour (meshtastic#5086) * Coerce minimum telemetry interval of 30 minutes on defaults and make new default interval one hour * Smaller log messages * Add buzzer feedback on GPS toggle (meshtastic#5090) Triple Press on buttons toggles GPS enable/disable. This enhancement plays a triple-beep so that users of devices with buzzers can get audible feedback about whether they have turned the GPS off or on. This is especially valuable for screenless devices such as the T1000E where it may not be immediately obvious the GPS has been disabled. --------- Co-authored-by: Ben Meadors <[email protected]> Co-authored-by: Technologyman00 <[email protected]>
…new default interval one hour (#5086) * Coerce minimum telemetry interval of 30 minutes on defaults and make new default interval one hour * Smaller log messages
|
Is there anyway to get around the limit? This killed my weather station as it can no longer update my private MQTT server fast enough |
Internally we've talked about the potential for use cases outside the normal defaults, and so far we've settled on encouraging people to compile the source themselves. Alternatively, we could consider allowing faster updates when not on the default channel. |
Starting to see Telemetry traffic quickly become the predominant generator of traffic on the public mesh. This is another attempt to back some of that off to make more headroom for text messaging, node discovery, and position updates, as well as prevent inadvertent setting of these values to spammy intervals. I don't need to see everybody's battery level updated every 5 minutes. ;-)
The new standard would be: