Skip to main content

Device Configuration

The device config options are: Role, Serial Output, and Debug Log. Device config uses an admin message sending a Config.Device protobuf.

Device Config Values

Roles

Device RoleDescriptionBest Uses
CLIENTApp connected or stand alone messaging device.General use for individuals needing to communicate over the Meshtastic network with support for client applications.
CLIENT_MUTEDevice that does not forward packets from other devices.Situations where a device needs to participate in the network without assisting in packet routing, reducing network load.
CLIENT_HIDDENDevice that only broadcasts as needed for stealth or power savings.Use in stealth/hidden deployments or to reduce airtime/power consumption while still participating in the network.
TRACKERBroadcasts GPS position packets as priority.Tracking the location of individuals or assets, especially in scenarios where timely and efficient location updates are critical.
LOST_AND_FOUNDBroadcasts location as message to default channel regularly for to assist with device recovery.Used for recovery efforts of a lost device.
SENSORBroadcasts telemetry packets as priority.Deploying in scenarios where gathering environmental or other sensor data is crucial, with efficient power usage and frequent updates.
TAKOptimized for ATAK system communication, reduces routine broadcasts.Integration with ATAK systems (via the Mesthastic ATAK Plugin) for communication in tactical or coordinated operations.
TAK_TRACKEREnables automatic TAK PLI broadcasts and reduces routine broadcasts.Standalone PLI integration with ATAK systems for communication in tactical or coordinated operations.
REPEATERInfrastructure node for extending network coverage by relaying messages with minimal overhead. Not visible in Nodes list.Best positioned in strategic locations to maximize the network's overall coverage. Device is not shown in topology.
ROUTERInfrastructure node for extending network coverage by relaying messages. Visible in Nodes list.Best positioned in strategic locations to maximize the network's overall coverage. Device is shown in topology.
ROUTER_CLIENTCombination of both ROUTER and CLIENT. Not for mobile devices.Devices in a strategic position for priority routing that need to also serve as a standard CLIENT.

Role Comparison

This table shows the default values after selecting a preset. As always, individual settings can be adjusted after choosing a preset.

Device RoleBluetooth/Wi-Fi EnabledScreen EnabledPower ConsumptionRetransmitPrioritized RoutingVisible in Nodes List
CLIENTYesYesRegularYesNoYes
CLIENT_MUTEYesYesLowestNoNoYes
CLIENT_HIDDENYesYesLowestLocal onlyNoNo
TRACKERYesNoRegularNoNoYes
LOST_AND_FOUNDYesNoRegularNoNoYes
SENSORYesNoHighNoNoYes
TAKYesOptionalRegularYesNoYes
TAK_TRACKERYesOptionalRegularYesNoYes
ROUTERNoNoHighYesYesYes
ROUTER_CLIENTYesYesHighestYesYesYes
REPEATERYesNoHighYesYesNo

Rebroadcast Mode

This setting defines the device's behavior for how messages are rebroadcasted.

ValueDescription
ALLALL (Default) - This setting will rebroadcast ALL messages from its primary mesh as well as other meshes with the same modem settings, including when encryption settings differ.
ALL_SKIP_DECODINGALL_SKIP_DECODING - Same as behavior as ALL, but skips packet decoding and simply rebroadcasts them. Only available with Repeater role.
LOCAL_ONLYLOCAL_ONLY - Ignores observed messages from foreign meshes that are open or those which it cannot decrypt. Only rebroadcasts message on the nodes local primary / secondary channels.
KNOWN_ONLYKNOWN_ONLY - Ignores observed messages from foreign meshes like LOCAL_ONLY, but takes it a step further by also ignoring messages from nodenums not in the node's known list (NodeDB).

Serial Console

Acceptable values: true or false

Disabling this will disable the SerialConsole by not initializing the StreamAPI.

Debug Log

Acceptable values: true or false

By default we turn off logging as soon as an API client connects. Set this to true to leave the debug log outputting even when API is active.

GPIO for user button

This is the GPIO pin number that will be used for the user button, if your device does not come with a predefined user button.

GPIO for PWM Buzzer

This is the GPIO pin number that will be used for the PWM buzzer, if your device does not come with a predefined buzzer.

Node Info Broadcast Seconds

This is the number of seconds between NodeInfo message broadcasts from the device. The device will still respond ad-hoc to NodeInfo messages when a response is wanted.

Double Tap as Button Press

This option will enable a double tap, when a supported accelerometer is attached to the device, to be treated as a button press.

Managed Mode

Enabling Managed mode will restrict access to all radio configurations via client applications. Radio configurations will only be accessible through the Admin channel. To avoid being locked out, make sure the Admin channel is working properly before enabling it.

Device Config Client Availability

Apple

info

All device config options other than NTP Server are available on iOS, iPadOS and macOS at Settings > Radio Configuration > Device.