RemoteHardwareModule Config


from message meshtastic.ModuleConfig.RemoteHardwareConfig




allowUndefinedPinAccess: boolean

Whether the Module allows consumers to read / write to pins not defined in available_pins


from field: bool allow_undefined_pin_access = 2;

availablePins: RemoteHardwarePin[]

Exposes the available pins to the mesh for reading and writing


from field: repeated meshtastic.RemoteHardwarePin available_pins = 3;

enabled: boolean

Whether the Module is enabled


from field: bool enabled = 1;

fields: FieldList
runtime: ProtoRuntime
typeName: "meshtastic.ModuleConfig.RemoteHardwareConfig" = "meshtastic.ModuleConfig.RemoteHardwareConfig"


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


    Returns ModuleConfig_RemoteHardwareConfig

  • Serialize the message to binary data.


    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().


    Returns JsonValue

  • Serialize the message to a JSON string.


    Returns string

Generated using TypeDoc