On the steep development curve of the cross-platform app, now it’s the crucial time to make the phone talk to the TTGO. Which means using protobufs.
After taking a deep look at the defined databags, here are a few considerations.
battery_level shouldn’t be here. I’d add accuracy, it is given by default by most geolocation plugins.
time should be renamed timestamp or sent_at as “time” is reserved in many languages.
Is there a real need for long_name and short_name? Can’t we just use a nickname and cap it to x chars so that it can fit on tiny screens too?
Move ModemConfig and other hardware settings to the more general “RadioConfig” protobuf for global hardware configurations.
// uint32 bandwidth = 5;
// int32 spread_factor = 6;
// int32 coding_rate = 7;
in the app there will be the possibility to switch to “Advanced Mode” and tune-up these parameters.
position_broadcast_secs : In another discussion it seemed we needed a spot position sharing pretty much like messaging apps where I can send my current position as a message to somebody.
Which ones of these should be configurable via app?
uint32 wait_bluetooth_secs = 4;
uint32 screen_on_secs = 5;
uint32 phone_timeout_secs = 6;
uint32 phone_sds_timeout_sec = 7;
uint32 mesh_sds_timeout_secs = 8;
uint32 sds_secs = 9;
uint32 ls_secs = 10;
uint32 min_wake_secs = 11;
ChannelSettings channel_settings = 2; why here? Isn’t RadioConfig supposed to be general?
wifi_ap_mode should be an enum supporting Access Point, Station and Off modes.
Clarification of these points will be very much appreciated for a deeper understanding of what kind of info is transmitted on the mesh and the inner tunings of meshtastic.