From e624b13434b3db202687aab80806b9de9f90b1c9 Mon Sep 17 00:00:00 2001 From: Sacha Weatherstone Date: Thu, 9 Dec 2021 19:21:30 +1100 Subject: [PATCH] Add get_owner_request & get_owner_respons variants --- admin.proto | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/admin.proto b/admin.proto index 1dea1a5..9eb12fa 100644 --- a/admin.proto +++ b/admin.proto @@ -5,8 +5,8 @@ option optimize_for = LITE_RUNTIME; option go_package = "github.com/meshtastic/gomeshproto"; import "channel.proto"; -import "mesh.proto"; import "radioconfig.proto"; +import "mesh.proto"; option java_outer_classname = "AdminProtos"; @@ -39,18 +39,24 @@ message AdminMessage { Channel set_channel = 3; /* - * Send the current RadioConfig in the response for this message. + * Send the current RadioConfig in the response to this message. */ bool get_radio_request = 4; RadioConfig get_radio_response = 5; /* - * Send the specified channel in the response for this message + * Send the specified channel in the response to this message * NOTE: This field is sent with the channel index + 1 (to ensure we never try to send 'zero' - which protobufs treats as not present) */ uint32 get_channel_request = 6; Channel get_channel_response = 7; + /* + * Send the current owner data in the response to this message. + */ + bool get_owner_request = 8; + User get_owner_response = 9; + /* * Setting channels/radio config remotely carries the risk that you might send an invalid config and the radio never talks to your mesh again. * Therefore if setting either of these properties remotely, you must send a confirm_xxx message within 10 minutes.