From 3bcab0e223986e86a8deec4af5fca9db2ae3ef9a Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 4 Sep 2023 18:38:58 -0500 Subject: [PATCH] [create-pull-request] automated change (#2768) Co-authored-by: thebentern --- protobufs | 2 +- src/mesh/generated/meshtastic/config.pb.h | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/protobufs b/protobufs index 468ff2e24..826dfb760 160000 --- a/protobufs +++ b/protobufs @@ -1 +1 @@ -Subproject commit 468ff2e2457d7534a907af0a21bdede9f4042cb7 +Subproject commit 826dfb760450a4225384da6316582e93138102ba diff --git a/src/mesh/generated/meshtastic/config.pb.h b/src/mesh/generated/meshtastic/config.pb.h index ef9d09a19..1114ea99b 100644 --- a/src/mesh/generated/meshtastic/config.pb.h +++ b/src/mesh/generated/meshtastic/config.pb.h @@ -51,8 +51,9 @@ typedef enum _meshtastic_Config_DeviceConfig_RebroadcastMode { } meshtastic_Config_DeviceConfig_RebroadcastMode; /* Bit field of boolean configuration options, indicating which optional - fields to include when assembling POSITION messages - Longitude and latitude are always included (also time if GPS-synced) + fields to include when assembling POSITION messages. + Longitude, latitude, altitude, speed, heading, and DOP + are always included (also time if GPS-synced) NOTE: the more fields are included, the larger the message will be - leading to longer airtime and a higher risk of packet loss */ typedef enum _meshtastic_Config_PositionConfig_PositionFlags {