Client device role
from enum value: CLIENT = 0;
Client Hidden device role Used for nodes that "only speak when spoken to" Turns all of the routine broadcasts but allows for ad-hoc communication Still rebroadcasts, but with local only rebroadcast mode (known meshes only) Can be used for clandestine operation or to dramatically reduce airtime / power consumption
from enum value: CLIENT_HIDDEN = 8;
Client Mute device role Same as a client except packets will not hop over this node, does not contribute to routing packets for mesh.
from enum value: CLIENT_MUTE = 1;
Lost and Found device role Used to automatically send a text message to the mesh with the current position of the device on a frequent interval: "I'm lost! Position: lat / long"
from enum value: LOST_AND_FOUND = 9;
Repeater device role Mesh packets will simply be rebroadcasted over this node. Nodes configured with this role will not originate NodeInfo, Position, Telemetry or any other packet type. They will simply rebroadcast any mesh packets on the same frequency, channel num, spread factor, and coding rate.
from enum value: REPEATER = 4;
Router device role. Mesh packets will prefer to be routed over this node. This node will not be used by client apps. The wifi/ble radios and the oled screen will be put to sleep. This mode may still potentially have higher power usage due to it's preference in message rebroadcasting on the mesh.
from enum value: ROUTER = 2;
Router Client device role Mesh packets will prefer to be routed over this node. The Router Client can be used as both a Router and an app connected Client.
from enum value: ROUTER_CLIENT = 3;
Sensor device role Telemetry Mesh packets will be prioritized higher and sent more frequently by default. When used in conjunction with power.is_power_saving = true, nodes will wake up, send environment telemetry, and then sleep for telemetry.environment_update_interval seconds.
from enum value: SENSOR = 6;
TAK device role Used for nodes dedicated for connection to an ATAK EUD. Turns off many of the routine broadcasts to favor CoT packet stream from the Meshtastic ATAK plugin -> IMeshService -> Node
from enum value: TAK = 7;
Tracker device role Position Mesh packets will be prioritized higher and sent more frequently by default. When used in conjunction with power.is_power_saving = true, nodes will wake up, send position, and then sleep for position.position_broadcast_secs seconds.
from enum value: TRACKER = 5;
Generated using TypeDoc
Defines the device's role on the Mesh network
Generated
from enum meshtastic.Config.DeviceConfig.Role