Data: Message<"meshtastic.Data"> & {
    bitfield?: number;
    dest: number;
    emoji: number;
    payload: Uint8Array;
    portnum: PortNum;
    replyId: number;
    requestId: number;
    source: number;
    wantResponse: boolean;
}

(Formerly called SubPacket) The payload portion fo a packet, this is the actual bytes that are sent inside a radio packet (because from/to are broken out by the comms library)

Type declaration

  • Optionalbitfield?: number

    Bitfield for extra flags. First use is to indicate that user approves the packet being uploaded to MQTT.

    from field: optional uint32 bitfield = 9;

  • dest: number

    The address of the destination node. This field is is filled in by the mesh radio device software, application layer software should never need it. RouteDiscovery messages must populate this. Other message types might need to if they are doing multihop routing.

    from field: fixed32 dest = 4;

  • emoji: number

    Defaults to false. If true, then what is in the payload should be treated as an emoji like giving a message a heart or poop emoji.

    from field: fixed32 emoji = 8;

  • payload: Uint8Array

    TODO: REPLACE

    from field: bytes payload = 2;

  • portnum: PortNum

    Formerly named typ and of type Type

    from field: meshtastic.PortNum portnum = 1;

  • replyId: number

    If set, this message is intened to be a reply to a previously sent message with the defined id.

    from field: fixed32 reply_id = 7;

  • requestId: number

    Only used in routing or response messages. Indicates the original message ID that this message is reporting failure on. (formerly called original_id)

    from field: fixed32 request_id = 6;

  • source: number

    The address of the original sender for this message. This field should only be populated for reliable multihop packets (to keep packets small).

    from field: fixed32 source = 5;

  • wantResponse: boolean

    Not normally used, but for testing a sender can request that recipient responds in kind (i.e. if it received a position, it should unicast back it's position). Note: that if you set this on a broadcast you will receive many replies.

    from field: bool want_response = 3;

from message meshtastic.Data