This message is never sent over the wire, but it is used for serializing DB state to flash in the device code FIXME, since we write this each time we enter deep sleep (and have infinite flash) it would be better to use some sort of append only data structure for the receive queue and use the preferences store for the other stuff

Generated

from message meshtastic.DeviceState

Hierarchy

Constructors

  • Parameters

    Returns DeviceState

Properties

didGpsReset: boolean

Some GPS receivers seem to have bogus settings from the factory, so we always do one factory reset.

Generated

from field: bool did_gps_reset = 11;

myNode?: MyNodeInfo

Read only settings/info about this node

Generated

from field: meshtastic.MyNodeInfo my_node = 2;

noSave: boolean

Used only during development. Indicates developer is testing and changes should never be saved to flash. Deprecated in 2.3.1

Generated

from field: bool no_save = 9 [deprecated = true];

Deprecated

nodeDbLite: NodeInfoLite[]

New lite version of NodeDB to decrease memory footprint

Generated

from field: repeated meshtastic.NodeInfoLite node_db_lite = 14;

nodeRemoteHardwarePins: NodeRemoteHardwarePin[]

The mesh's nodes with their available gpio pins for RemoteHardware module

Generated

from field: repeated meshtastic.NodeRemoteHardwarePin node_remote_hardware_pins = 13;

owner?: User

My owner info

Generated

from field: meshtastic.User owner = 3;

receiveQueue: MeshPacket[]

Received packets saved for delivery to the phone

Generated

from field: repeated meshtastic.MeshPacket receive_queue = 5;

rxTextMessage?: MeshPacket

We keep the last received text message (only) stored in the device flash, so we can show it on the screen. Might be null

Generated

from field: meshtastic.MeshPacket rx_text_message = 7;

rxWaypoint?: MeshPacket

We keep the last received waypoint stored in the device flash, so we can show it on the screen. Might be null

Generated

from field: meshtastic.MeshPacket rx_waypoint = 12;

version: number

A version integer used to invalidate old save files when we make incompatible changes This integer is set at build time and is private to NodeDB.cpp in the device code.

Generated

from field: uint32 version = 8;

fields: FieldList
runtime: ProtoRuntime
typeName: "meshtastic.DeviceState" = "meshtastic.DeviceState"

Methods

  • Create a deep copy.

    Returns DeviceState

  • Compare with a message of the same type. Note that this function disregards extensions and unknown fields.

    Parameters

    Returns boolean

  • Parse 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.

    Parameters

    • bytes: Uint8Array
    • Optional options: Partial<BinaryReadOptions>

    Returns this

  • Parse a message from a JSON value.

    Parameters

    • jsonValue: JsonValue
    • Optional options: Partial<JsonReadOptions>

    Returns this

  • Parse a message from a JSON string.

    Parameters

    • jsonString: string
    • Optional options: Partial<JsonReadOptions>

    Returns this

  • Retrieve the MessageType of this message - a singleton that represents the protobuf message declaration and provides metadata for reflection- based operations.

    Returns MessageType<DeviceState>

  • Serialize the message to binary data.

    Parameters

    • Optional options: Partial<BinaryWriteOptions>

    Returns Uint8Array

  • Override 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.

    Returns JsonValue

  • Serialize the message to a JSON value, a JavaScript value that can be passed to JSON.stringify().

    Parameters

    • Optional options: Partial<JsonWriteOptions>

    Returns JsonValue

  • Serialize the message to a JSON string.

    Parameters

    • Optional options: Partial<JsonWriteStringOptions>

    Returns string

  • Parameters

    Returns boolean

  • Parameters

    • bytes: Uint8Array
    • Optional options: Partial<BinaryReadOptions>

    Returns DeviceState

  • Parameters

    • jsonValue: JsonValue
    • Optional options: Partial<JsonReadOptions>

    Returns DeviceState

  • Parameters

    • jsonString: string
    • Optional options: Partial<JsonReadOptions>

    Returns DeviceState

Generated using TypeDoc