The packet id, used to allow the phone to request missing read packets from the FIFO, see our bluetooth docs
from field: uint32 id = 1;
Log levels, chosen to match python logging conventions.
Log levels, chosen to match python logging conventions.
from field: meshtastic.MeshPacket packet = 2;
Tells the phone what our node number is, can be -1 if we've not yet joined a mesh. NOTE: This ID must not change - to keep (minimal) compatibility with <1.2 version of android apps.
from field: meshtastic.MyNodeInfo my_info = 3;
One packet is sent for each node in the on radio DB starts over with the first node in our DB
from field: meshtastic.NodeInfo node_info = 4;
Include a part of the config (was: RadioConfig radio)
from field: meshtastic.Config config = 5;
Set to send debug console output over our protobuf stream
from field: meshtastic.LogRecord log_record = 6;
Sent as true once the device has finished sending all of the responses to want_config recipient should check if this ID matches our original request nonce, if not, it means your config responses haven't started yet. NOTE: This ID must not change - to keep (minimal) compatibility with <1.2 version of android apps.
from field: uint32 config_complete_id = 7;
Sent to tell clients the radio has just rebooted. Set to true if present. Not used on all transports, currently just used for the serial console. NOTE: This ID must not change - to keep (minimal) compatibility with <1.2 version of android apps.
from field: bool rebooted = 8;
Include module config
from field: meshtastic.ModuleConfig moduleConfig = 9;
One packet is sent for each channel
from field: meshtastic.Channel channel = 10;
Queue status info
from field: meshtastic.QueueStatus queueStatus = 11;
File Transfer Chunk
from field: meshtastic.XModem xmodemPacket = 12;
Device metadata message
from field: meshtastic.DeviceMetadata metadata = 13;
MQTT Client Proxy Message (device sending to client / phone for publishing to MQTT)
from field: meshtastic.MqttClientProxyMessage mqttClientProxyMessage = 14;
File system manifest messages
from field: meshtastic.FileInfo fileInfo = 15;
Notification message to the client
from field: meshtastic.ClientNotification clientNotification = 16;
Optional value?: undefinedfrom oneof meshtastic.FromRadio.payload_variant
Static Readonly fieldsStatic Readonly runtimeStatic Readonly typeParse from binary data, merging fields.
Repeated fields are appended. Map entries are added, overwriting existing keys.
If a message field is already present, it will be merged with the new data.
Optional options: Partial<BinaryReadOptions>Protected toJSONOverride for serialization behavior. This will be invoked when calling JSON.stringify on this message (i.e. JSON.stringify(msg)).
Note that this will not serialize google.protobuf.Any with a packed message because the protobuf JSON format specifies that it needs to be unpacked, and this is only possible with a type registry to look up the message type. As a result, attempting to serialize a message with this type will throw an Error.
This method is protected because you should not need to invoke it directly -- instead use JSON.stringify or toJsonString for stringified JSON. Alternatively, if actual JSON is desired, you should use toJson.
Static equalsStatic fromStatic fromStatic fromGenerated using TypeDoc
Packets from the radio to the phone will appear on the fromRadio characteristic. It will support READ and NOTIFY. When a new packet arrives the device will BLE notify? It will sit in that descriptor until consumed by the phone, at which point the next item in the FIFO will be populated.
Generated
from message meshtastic.FromRadio